Bug 848954 - Putting private key first in SSLProxyMachineCertificateFile causes segfault
Putting private key first in SSLProxyMachineCertificateFile causes segfault
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: httpd (Show other bugs)
i686 Linux
low Severity low
: rc
: ---
Assigned To: Jan Kaluža
Zbysek MRAZ
Depends On:
  Show dependency treegraph
Reported: 2012-08-16 18:34 EDT by Orion Poplawski
Modified: 2013-07-03 09:16 EDT (History)
2 users (show)

See Also:
Fixed In Version: httpd-2.2.15-17.el6
Doc Type: Bug Fix
Doc Text:
Cause: mod_ssl presumed the private key is set after the certificate in SSLProxyMachineCertificateFile. Consequence: httpd crashed if the private key had been set before the certificate in SSLProxyMachineCertificateFile. Fix: mod_ssl was fixed to check if the private key was set before the certificate. Result: mod_ssl does not crash in this situation and prints error message instead.
Story Points: ---
Clone Of:
Last Closed: 2013-02-21 05:17:45 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Apache Bugzilla 52212 None None None 2012-08-16 18:34:52 EDT
Red Hat Product Errata RHSA-2013:0512 normal SHIPPED_LIVE Low: httpd security, bug fix, and enhancement update 2013-02-20 16:29:30 EST

  None (edit)
Description Orion Poplawski 2012-08-16 18:34:52 EDT
Description of problem:

If you put the private key first in the SSLProxyMachineCertificateFile, the apache handler process will segfault on connection.  See upstream bug report for more info.  Putting the certificate first fixes.

Version-Release number of selected component (if applicable):

How reproducible:
Comment 2 Joe Orton 2012-08-17 08:05:16 EDT
Fixed upstream.

Comment 3 Joe Orton 2012-08-17 08:05:31 EDT
Thanks for the report, Orion.
Comment 8 errata-xmlrpc 2013-02-21 05:17:45 EST
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.


Note You need to log in before you can comment on or make changes to this bug.