Your submission was sent successfully! Close

Thank you for contacting us. A member of our team will be in touch shortly. Close

You have successfully unsubscribed! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates about Ubuntu and upcoming events where you can meet our team.Close

CVE-2013-7040

Publication date 19 May 2014

Last updated 24 July 2024


Ubuntu priority

Python 2.7 before 3.4 only uses the last eight bits of the prefix to randomize hash values, which causes it to compute hash values without restricting the ability to trigger hash collisions predictably and makes it easier for context-dependent attackers to cause a denial of service (CPU consumption) via crafted input to an application that maintains a hash table. NOTE: this vulnerability exists because of an incomplete fix for CVE-2012-1150.

Read the notes from the security team

Status

Package Ubuntu Release Status
python2.6 14.04 LTS trusty Not in release
13.10 saucy Not in release
13.04 raring Not in release
12.10 quantal Not in release
12.04 LTS precise Not in release
10.04 LTS lucid Ignored
python2.7 14.04 LTS trusty Ignored
13.10 saucy Ignored
13.04 raring Ignored end of life
12.10 quantal Ignored end of life
12.04 LTS precise Ignored
10.04 LTS lucid Not in release
python3.1 14.04 LTS trusty Not in release
13.10 saucy Not in release
13.04 raring Not in release
12.10 quantal Not in release
12.04 LTS precise Not in release
10.04 LTS lucid Ignored end of life
python3.2 14.04 LTS trusty Not in release
13.10 saucy Not in release
13.04 raring Not in release
12.10 quantal Ignored end of life
12.04 LTS precise Ignored
10.04 LTS lucid Not in release
python3.3 14.04 LTS trusty Not in release
13.10 saucy Ignored
13.04 raring Ignored end of life
12.10 quantal Ignored end of life
12.04 LTS precise Not in release
10.04 LTS lucid Not in release

Notes


mdeslaur

This is being fixed upstream by changing the hashing algorithm to SipHash in python 3.4. See http://www.python.org/dev/peps/pep-0456/ Upstream has no intention of backporting this change to stable releases. We will not be fixing this in older releases.