Bug 10989 - python new security issue CVE-2013-4238
Summary: python new security issue CVE-2013-4238
Alias: None
Product: Mageia
Classification: Unclassified
Component: Security (show other bugs)
Version: 3
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: QA Team
QA Contact: Sec team
URL: http://lwn.net/Vulnerabilities/564820/
Whiteboard: MGA2TOO has_procedure mga3-64-ok mga2...
Keywords: validated_update
Depends on: 10391
Blocks: 10102
  Show dependency treegraph
Reported: 2013-08-13 03:15 CEST by David Walser
Modified: 2013-08-26 21:12 CEST (History)
6 users (show)

See Also:
Source RPM: python
Status comment:


Description David Walser 2013-08-13 03:15:45 CEST
A CVE has been assigned to Python upstream issue 18709:

Proposed patches to fix it have been attached to the upstream issue report.

Oden has added these patches in Cauldron, as well as Mageia 2 and Mageia 3.

Note that there is also a PoC attached to the upstream issue report.

Given the mention of ssl.match_hostname on the upstream issue report, I wonder if this is related to CVE-2013-2099 (Bug 10391).

I'm not assigning this to QA just yet, as discussion of this is continuing as we speak on the upstream issue report.

If it's decided to go ahead with these patches, we'll fix CVE-2013-2099 for python3 in the process, as the patch for that was already in SVN.


Steps to Reproduce:
David Walser 2013-08-13 03:16:12 CEST

CC: (none) => makowski.mageia
Blocks: (none) => 10391
Whiteboard: (none) => MGA2TOO

Comment 1 Oden Eriksson 2013-08-13 07:40:42 CEST
A CVE was assigned as CVE-2013-4073 was for ruby.

New CVE is CVE-2013-4238 as of:


CC: (none) => oe
Summary: python, python3 new security issue CVE-2013-4073 => python, python3 new security issue CVE-2013-4238

Comment 2 Philippe Makowski 2013-08-13 12:12:42 CEST
so we should release an update for python and python3 for mga 3 with the patch included ?
if yes, I can take care of and at the same time fix mga 10102 for Python 3
Comment 3 David Walser 2013-08-13 13:19:37 CEST
Oden, thanks for updating the correct CVE number.

Philippe, the patch(es) for this are already committed, so if there are any further fixes you want to commit, go ahead, and we can fix this one with the same update.

Severity: normal => major

Comment 4 Philippe Makowski 2013-08-13 13:52:31 CEST
done for mga3 rev 466128, this should fix MGA#10102
Comment 5 Philippe Makowski 2013-08-14 21:25:05 CEST
python3-3.3.0-4.3.mga3 is update testing 
I guess that Oden did all the others builds need
Comment 6 David Walser 2013-08-14 22:09:52 CEST
Philippe, do you have some information to add to the advisory describing what else you've fixed?
Comment 7 Philippe Makowski 2013-08-14 22:20:05 CEST
This fix MGA#10102  : "Unable to install Python packages with C extensions via pip and virtualenv" :
Before the fix installing Python packages via pip inside a virtualenv fails if the Python package uses a C extension.
David Walser 2013-08-15 04:00:56 CEST

Blocks: (none) => 9395, 10102

Comment 8 David Walser 2013-08-15 17:08:25 CEST
OK, let's use this bug for the python update and Bug 10391 for the python3 update.


Updated python packages fix security vulnerability:

Ryan Sleevi of the Google Chrome Security Team has discovered that Python's SSL
module doesn't handle NULL bytes inside subjectAltNames general names. This
could lead to a breach when an application uses ssl.match_hostname() to match
the hostname againt the certificate's subjectAltName's dNSName general names.

Additionally, an issue with installing Python packages with C extensions via
pip and virtualenv has been fixed in Mageia 3 (mga#10102).


Updated packages in core/updates_testing:

from SRPMS:

Blocks: 9395 => (none)
Assignee: bugsquad => qa-bugs

David Walser 2013-08-15 17:08:42 CEST

Blocks: 10391 => (none)
Depends on: (none) => 10391

claire robinson 2013-08-15 18:21:49 CEST

Summary: python, python3 new security issue CVE-2013-4238 => python new security issue CVE-2013-4238
Source RPM: python, python3 => python

Comment 9 David Walser 2013-08-15 19:23:38 CEST
The bug title (with python3) was correct, as this CVE affects both python and python3.  I used the other bug (Bug 10391) to handle the python3 update to separate these and make it easier for QA, but we are fixing this CVE for python3 as well.
Comment 10 claire robinson 2013-08-16 13:33:34 CEST
No PoC so just testing python & tkinter using random examples from here, run in idle: http://wiki.python.org/moin/SimplePrograms
claire robinson 2013-08-16 13:33:45 CEST

Whiteboard: MGA2TOO => MGA2TOO has_procedure

Comment 11 claire robinson 2013-08-16 13:44:43 CEST
Testing complete mga3 64

Whiteboard: MGA2TOO has_procedure => MGA2TOO has_procedure mga3-64-ok

Comment 12 claire robinson 2013-08-16 14:01:31 CEST
Testing complete mga2 64

Whiteboard: MGA2TOO has_procedure mga3-64-ok => MGA2TOO has_procedure mga3-64-ok mga2-64-ok

Comment 13 David Walser 2013-08-16 14:15:47 CEST
There's a PoC attached here:
Comment 14 claire robinson 2013-08-16 14:18:41 CEST
Advisory uploaded.
Comment 15 claire robinson 2013-08-16 16:25:55 CEST
No idea how to use the certificate on the link David. If you can point us in the right direction I'm happy to check it again.

Testing complete mga2-32 for now.

Whiteboard: MGA2TOO has_procedure mga3-64-ok mga2-64-ok => MGA2TOO has_procedure mga3-64-ok mga2-32-ok mga2-64-ok

Comment 16 David Walser 2013-08-16 17:17:24 CEST
Yeah, sorry.  I just looked at the ssl module and I don't even see match_hostname(), so I don't know how to use it either.
Comment 17 David GEIGER 2013-08-17 08:53:52 CEST
Testing complete mag3_32, ok for me nothing to report python works fine.

CC: (none) => geiger.david68210
Whiteboard: MGA2TOO has_procedure mga3-64-ok mga2-32-ok mga2-64-ok => MGA2TOO has_procedure mga3-64-ok mga2-32-ok mga2-64-ok mga3-32-ok

Comment 18 claire robinson 2013-08-17 09:56:32 CEST

Could sysadmin please push from 2 & 3 core/updates_testing to updates


Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs

Comment 19 Thomas Backlund 2013-08-17 10:45:16 CEST
Update pushed:

CC: (none) => tmb
Resolution: (none) => FIXED

Comment 20 David Walser 2013-08-26 18:56:30 CEST
Looks like I screwed up on this one...the correct CVE is 4238, as it says in the bug title.  The advisory has it typoed as 4328.  This also happened in the Bug 10391 update.

URL: (none) => http://lwn.net/Vulnerabilities/564820/

Comment 21 Dave Hodgins 2013-08-26 21:12:41 CEST
Advisory 10989.adv corrected in svn.

CC: (none) => davidwhodgins

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