RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1087838 - backport nscd netgroup caching fixes from upstream
Summary: backport nscd netgroup caching fixes from upstream
Keywords:
Status: CLOSED DUPLICATE of bug 1043557
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: glibc
Version: 6.5
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Carlos O'Donell
QA Contact: qe-baseos-tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-15 12:34 UTC by Michael Weiser
Modified: 2016-11-24 12:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-04-15 14:15:18 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Michael Weiser 2014-04-15 12:34:19 UTC
Description of problem:
netgroup caching in nscd has several problems that have been fixed upstream. For example, one is caused by improper usage of extend_alloca, causing nscd to segfault if a long netgroup entry is added to /etc/netgroup. If it doesn't segfault, the improperly extended buffer contains garbage or is missing part of the netgroup data, causing all kinds of weird behaviour (e.g. group membership not being seen by sudo and others).

This has been fixed upstream with this commit: https://sourceware.org/git/?p=glibc.git;a=commitdiff_plain;h=980cb5180e1b71224a57ca52b995c959b7148c09

Version-Release number of selected component (if applicable):
nscd-2.12-1.132.el6

How reproducible:
always

Steps to Reproduce:
1. add long entry (>1024 bytes) to /etc/netgroup
2. enable netgroup caching in nscd
3. clear netgroup cache
4. getent netgroup longnetgroupentry

Actual results:
nscd segfaults or returns incomplete netgroup entry

[root@de-do-rzcfx211 ~]# rm -f /var/db/nscd/netgroup ; nscd -d
Tue 15 Apr 2014 02:33:31 PM CEST - 23139: handle_request: request received (Version = 2) from PID 23149
Tue 15 Apr 2014 02:33:31 PM CEST - 23139:       GETFDNETGR
Tue 15 Apr 2014 02:33:31 PM CEST - 23139: provide access to FD 13, for netgroup
Tue 15 Apr 2014 02:33:31 PM CEST - 23139: handle_request: request received (Version = 2) from PID 23149
Tue 15 Apr 2014 02:33:31 PM CEST - 23139:       GETNETGRENT (test)
Tue 15 Apr 2014 02:33:31 PM CEST - 23139: Haven't found "test" in netgroup cache!
Segmentation fault

Expected results:
nscd doesn't segfault and returns complete netgroup entry

Workaround:
Disable netgroup caching in /etc/nscd.conf.

Comment 2 Siddhesh Poyarekar 2014-04-15 14:15:18 UTC
Thanks for the report.  We are considering most of those fixes for backport into rhel-6.  The patch you mentioned will likely make it into 6.6 assuming that no problems turn up due to it.

*** This bug has been marked as a duplicate of bug 1043557 ***


Note You need to log in before you can comment on or make changes to this bug.