Red Hat Bugzilla – Bug 816203
yppasswd doesn't handle crypt() returning NULL
Last modified: 2013-03-13 13:55:29 EDT
+++ This bug was initially created as a clone of Bug #814803 +++
Created attachment 579069 [details]
yp-tools spec file
yppasswd doesn't handle crypt() returning NULL, which is possible in fips mode and other corner conditions. It blindly tries to sntrcmp or strdup the return
values of crypt()
Attached is a patch and updated spec file for rawhide
--- Additional comment from firstname.lastname@example.org on 2012-04-20 13:48:13 EDT ---
Created attachment 579072 [details]
patch hanlding crypt() returning NULL
As I do not have an existing YP/NIS setup, someone should really test this patch
--- Additional comment from email@example.com on 2012-04-23 09:18:49 EDT ---
Thanks for reporting. I've pushed the patch to upstream, applied in Rawhide and will update in F17 soon.
Right now, I'm not going to apply the patch and update in F16 and F15 though, unless there is a real use case requiring this fix or some more significant fix.
--- Additional comment from firstname.lastname@example.org on 2012-04-23 09:20:45 EDT ---
yp-tools-2.12-9.fc17 has been submitted as an update for Fedora 17.
--- Additional comment from email@example.com on 2012-04-23 22:12:48 EDT ---
no need for f16, f15. Though RHEL would be nice :)
--- Additional comment via e-mail from firstname.lastname@example.org on 2012-04-23 23:19:48 EDT ---
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.
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.
Created attachment 656639 [details]
Patch which prints error and exists when crypt fails
There is no chance to fix this in RHEL-5 any more, since RHEL 5.10 is going to include only serious fixes.