Hide Forgot
Description of problem: This issue was found by Coverity: 1. Defect type: USE_AFTER_FREE ¶ 41. nss-pam-ldapd-0.7.5/nss/networks.c:122: pass_closed_arg: Passing closed handle "fp->fd" as an argument to "tio_skipall". Expand 2. Defect type: USE_AFTER_FREE 38. nss-pam-ldapd-0.7.5/nss/networks.c:105: pass_closed_arg: Passing closed handle "fp->fd" as an argument to "tio_skipall". Expand 3. Defect type: USE_AFTER_FREE 40. nss-pam-ldapd-0.7.5/nss/hosts.c:208: pass_closed_arg: Passing closed handle "fp->fd" as an argument to "tio_skipall". Expand 4. Defect type: USE_AFTER_FREE 39. nss-pam-ldapd-0.7.5/nss/hosts.c:176: pass_closed_arg: Passing closed handle "fp->fd" as an argument to "tio_skipall". Version-Release number of selected component (if applicable): How reproducible: not sure. We should make sure getent hosts and getent networks still works.
Not 100% sure if this is the same issue but it is likely this: http://lists.arthurdejong.org/nss-pam-ldapd-users/2014/msg00042.html and fixed by: http://arthurdejong.org/git/nss-pam-ldapd/commit/?id=1a59c4e3945dedafc8e63dc2688ddf035f0af656 The commit is on top of 0.7.19 but was never part of a 0.7 release. The fix was released in 0.8.14 and 0.9.3.
(In reply to Arthur de Jong from comment #1) > Not 100% sure if this is the same issue but it is likely this: Not completely, this one was caused by my sloppy backporting of a tio.c patch :-) > http://lists.arthurdejong.org/nss-pam-ldapd-users/2014/msg00042.html > and fixed by: > > http://arthurdejong.org/git/nss-pam-ldapd/commit/ > ?id=1a59c4e3945dedafc8e63dc2688ddf035f0af656 > > The commit is on top of 0.7.19 but was never part of a 0.7 release. The fix > was released in 0.8.14 and 0.9.3. Yes, this is exactly what I was about to commit. Thanks for chiming in!
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-0758.html