Red Hat Bugzilla – Bug 816981
yppasswdd doesn't handle crypt() returning NULL
Last modified: 2013-02-21 03:43:05 EST
Description of problem:
yppasswd doesn't handle crypt() returning NULL, which is possible in fips mode
and other corner conditions. It blindly tries to strcmp the returned
values of crypt()
--- Additional comment via e-mail from firstname.lastname@example.org on 2012-04-23 23:19:48
The Single Unix Spec documents crypt() as being able to return NULL under
certain conditions that are not related to FIPS. So, all software needs to
handle this possibility. But there have been some recent changes in glibc that
make it more likely that you will hit this. Especially if the user can control
the input. I'd update everywhere that you can get a QE slot. RHEL5 FIPS support
is supposed to be good. But I don't know if the glibc developers also updated
it in a way that makes this more likely now.
Version-Release number of selected component (if applicable):
Similar bug is in yp-tools: bug#816201
Created attachment 580741 [details]
patch hanlding crypt() returning NULL
This request was evaluated by Red Hat Product Management for
inclusion in a Red Hat Enterprise Linux release. Product
Management has requested further review of this request by
Red Hat Engineering, for potential inclusion in a Red Hat
Enterprise Linux release for currently deployed products.
This request is not yet committed for inclusion in a release.
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.