Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When a certificate bag in a PKCS12 file has no friendly name, PKCS12_parse will leak 1 byte on every call.
Version-Release number of selected component (if applicable):
1.0.1e-30
How reproducible:
Always
Steps to Reproduce:
1. Create a PKCS12 structure with a certificate that has no friendly name. PKCS12_create should easily create such a structure.
2. Call PKCS12_parse to get the certificate back out. Free the certificate, key, and ca stack.
3. Run with valgrind to show that 1 byte has been leaked from the call.
Actual results:
Memory leak
Expected results:
All memory freed
Additional info:
This is fixed in OpenSSL 1.0.2a (crypto/pkcs12/p12_kiss.c)
Is it possible to trigger with just command line tools?
I used the following command to generate certificates:
openssl req -x509 -newkey rsa -keyout localhost.key -out localhost.crt -nodes -batch -subj /CN=localhost
and then the following command to create the PKCS#12 file:
openssl pkcs12 -export -out localhost.pfx -inkey localhost.key -in localhost.crt -passout pass:
and one with a bag name:
openssl pkcs12 -export -out localhost-name.pfx -name server-certificate -inkey localhost.key -in localhost.crt -passout pass:
and then tried to reproduce using:
valgrind openssl pkcs12 -in localhost.pfx -passin pass: -passout pass:
And I see no difference in bytes reported by valgrind as either lost, reachable or suppressed. It's always 416 on x86_64.
Even a "noop" for openssl:
valgrind openssl < /dev/null
results in 416 bytes "still reachable".
The reproducer is:
openssl pkcs12 -export -out localhost.pfx -name "" -inkey localhost.key -in localhost.crt -passout pass:
valgrind openssl x509 -inform PKCS12 -in localhost.pfx
That command above actually does not properly load the certs from the PKCS12 file, but the leak is visible.
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.
https://rhn.redhat.com/errata/RHBA-2016-0933.html