Bug 689776
| Summary: | Certmonger segfaults when certificate request contains non-existent NSS database directory. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Kaleem <ksiddiqu> |
| Component: | certmonger | Assignee: | Nalin Dahyabhai <nalin> |
| Status: | CLOSED ERRATA | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1 | CC: | dpal, jgalipea, kchamart, syeghiay |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | certmonger-0.38-1.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, the certmonger service terminated unexpectedly if the user attempted to use a certificate database stored in a non-existent directory. While preparing an error message to return to its client, the daemon attempted to use already-freed memory, which could have caused a segmentation fault. With this update, certmonger displays a message that the directory does not exist and remains stable in these circumstances.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-05-19 13:07:20 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Kaleem
2011-03-22 12:33:04 UTC
(1)While verifying i found that with non-existent NSS database directory, now Segmentation fault is not there but following unhelpful message is displayed on console.
[root@jupiter ~]# selfsign-getcert request -d /tmp/kaleem -n test
(null)Error org.fedorahosted.certmonger.bad_arg.
Is this ok?
(2)I also observed that now when i am issuing duplicate request, it displays following on console.
[root@dhcp193-17 ~]# selfsign-getcert request -d /tmp/kaleem -n test
(null)Error org.fedorahosted.certmonger.duplicate
while earlier with certmonger-0.34 it was displaying,
[root@dhcp193-17 ~]# selfsign-getcert request -d /tmp/kaleem -n test
Error org.fedorahosted.certmonger.duplicate: Certificate at same location is already used by request "20110324065406".
(In reply to comment #3) > (1)While verifying i found that with non-existent NSS database directory, now > Segmentation fault is not there but following unhelpful message is displayed on > console. > > [root@jupiter ~]# selfsign-getcert request -d /tmp/kaleem -n test > (null)Error org.fedorahosted.certmonger.bad_arg. > > Is this ok? No, that's a bug. (Usually, the presence of "(null)" indicates that a NULL pointer is being used as a printable string, which shouldn't happen.) Verfied. RHEL version: [root@dhcp193-17 ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.1 Beta (Santiago) Certmonger Version: [root@dhcp193-17 ~]# rpm -qai certmonger |head Name : certmonger Relocations: (not relocatable) Version : 0.39 Vendor: Red Hat, Inc. Release : 1.el6 Build Date: Fri 25 Mar 2011 11:49:35 PM IST Install Date: Mon 28 Mar 2011 10:39:04 AM IST Build Host: x86-002.build.bos.redhat.com Group : System Environment/Daemons Source RPM: certmonger-0.39-1.el6.src.rpm Size : 678726 License: GPLv3+ Signature : (none) Packager : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla> URL : http://certmonger.fedorahosted.org Summary : Certificate status monitor and PKI enrollment client Steps used to verify: (1)Install certmonger [root@dhcp193-17 ~]# yum install certmonger -y Loaded plugins: product-id, subscription-manager Updating Red Hat repositories. INFO:rhsm-app.repolib:repos updated: 0 Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package certmonger.x86_64 0:0.39-1.el6 will be installed --> Finished Dependency Resolution Dependencies Resolved ============================================================================================================================================================= Package Arch Version Repository Size ============================================================================================================================================================= Installing: certmonger x86_64 0.39-1.el6 rhel6.1 175 k Transaction Summary ============================================================================================================================================================= Install 1 Package(s) Total download size: 175 k Installed size: 663 k Downloading Packages: certmonger-0.39-1.el6.x86_64.rpm | 175 kB 00:00 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Warning: RPMDB altered outside of yum. Installing : certmonger-0.39-1.el6.x86_64 1/1 duration: 91(ms) Installed products updated. Installed: certmonger.x86_64 0:0.39-1.el6 Complete! (2)Start certmonger service [root@dhcp193-17 ~]# service certmonger start Starting certmonger: [ OK ] (3)Issue a certificate request with non-existent database directory [root@dhcp193-17 ~]# selfsign-getcert request -d /tmp/kaleem/ -n test The location "/tmp/kaleem" must be a directory. Result: Now proper message is displayed on console for non-existent directory.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Previously, the certmonger service terminated unexpectedly if the user attempted to use a certificate database stored in a non-existent directory. While preparing an error message to return to its client, the daemon attempted to use already-freed memory, which could have caused a segmentation fault. With this update, certmonger displays a message that the directory does not exist and remains stable in these circumstances.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0570.html |