Red Hat Bugzilla – Bug 816984
yppasswdd doesn't handle crypt() returning NULL
Last modified: 2013-03-13 13:42:10 EDT
Description of problem:
yppasswdd 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 email@example.com 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#816203
Created attachment 580742 [details]
patch hanlding crypt() returning NULL
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.
There is no chance to fix this in RHEL-5 any more, since RHEL 5.10 is going to include only serious fixes.