Bug 1388635 - glibc: nss_db: get*ent crashes without preceding set*ent
Summary: glibc: nss_db: get*ent crashes without preceding set*ent
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: glibc
Version: 7.2
Hardware: All
OS: Linux
urgent
medium
Target Milestone: rc
: ---
Assignee: Carlos O'Donell
QA Contact: Michael Petlan
URL:
Whiteboard:
Depends On: 1213603
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-25 19:35 UTC by Marcel Kolaja
Modified: 2020-02-14 18:03 UTC (History)
12 users (show)

Fixed In Version: glibc-2.17-157.el7_3.1
Doc Type: Bug Fix
Doc Text:
Previously, Name Service Switch (NSS) module using hash-indexed files (nss_db)initialized itself incorrectly. Consequently, when nss_db module was enabled and any of the get*ent functions, such as getservent(), was called before a corresponding set*ent call, the application that called get*ent terminated unexpectedly. With this update, nss_db initialization sequence is fixed. As a result, calling get*ent functions without first calling set*ent works as expected, and the application no longer crashes.
Clone Of: 1213603
Environment:
Last Closed: 2016-12-06 17:05:35 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2861 0 normal SHIPPED_LIVE glibc bug fix update 2016-12-06 22:00:44 UTC
Sourceware 20237 0 None None None 2016-10-25 19:35:41 UTC

Description Marcel Kolaja 2016-10-25 19:35:31 UTC
This bug has been copied from bug #1213603 and has been proposed
to be backported to 7.3 z-stream (EUS).

Comment 5 Michael Petlan 2016-11-08 19:02:18 UTC
Reproduced with: glibc-2.17-157.el7
Verified with:   glibc-2.17-157.el7_3.1

VERIFIED.

Comment 7 errata-xmlrpc 2016-12-06 17:05:35 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2861.html


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