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.
Bug 928390 - Python SSLSocket.getpeercert() incorrectly returns an empty Subject Alternative Name from peer certificate.
Summary: Python SSLSocket.getpeercert() incorrectly returns an empty Subject Alternati...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: python
Version: 6.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Matej Stuchlik
QA Contact: Jan Kepler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-27 14:42 UTC by Ken Giusti
Modified: 2018-12-03 18:33 UTC (History)
7 users (show)

Fixed In Version: python-2.6.6-47.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-21 09:14:08 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Fix backported from 2.7 (471 bytes, patch)
2013-06-11 12:25 UTC, Matej Stuchlik
no flags Details | Diff


Links
System ID Private Priority Status Summary Last Updated
Python 13034 0 None None None Never
Red Hat Bugzilla 885173 1 None None None 2021-01-20 06:05:38 UTC
Red Hat Product Errata RHSA-2013:1582 0 normal SHIPPED_LIVE Moderate: python security, bug fix, and enhancement update 2013-11-20 21:39:43 UTC

Internal Links: 885173

Description Ken Giusti 2013-03-27 14:42:29 UTC
Description of problem:

As documented, SSLSocket.getpeercert() should provide access to the Subject Alternate Name field from the peer's certificate.  A bug in python will result in the Subject Alternate Name field to not be available to the application.

This could cause a false authentication failure if the application performs certificate hostname checking.

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

python-2.6.6-36

How reproducible:

100%

Steps to Reproduce:
1. python client connects to SSL server which has a SAN in its certificate
2. Have python access the certificate via getpeercert()
3. The returned map should have an entry for 'subjectAltName'
  
Actual results:

No entry for 'subjectAltName'

Expected results:

The map contains a 'subjectAltName' entry with a value that matches the SAN from the peer certificate.

Additional info:

The fix for this bug is straightforward, and has been fixed upstream in 2.7.3.  See http://bugs.python.org/issue13034

Comment 2 Bohuslav "Slavek" Kabrda 2013-05-22 12:44:38 UTC
This patch will work ok with RHEL 6 Python 2.6.

Comment 3 Matej Stuchlik 2013-06-11 12:25:46 UTC
Created attachment 759603 [details]
Fix backported from 2.7

Comment 11 errata-xmlrpc 2013-11-21 09:14:08 UTC
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.

http://rhn.redhat.com/errata/RHSA-2013-1582.html


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