Strix
26.1K

CVE-2013-7040

UnknownEPSS 3.26%

Last modified

CVE-2013-7040 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 3.26% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
3.26%

86.7th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersionsUpdate
AppleMac Os X<= 10.10.4—
PythonPython2.7.1—
PythonPython2.7.2Rc1
PythonPython2.7.3—
PythonPython2.7.4—
PythonPython2.7.5—
PythonPython2.7.6—
PythonPython2.7.7—
PythonPython2.7.1150—
PythonPython2.7.2150—
PythonPython3.0—
PythonPython3.0.1—
PythonPython3.1—
PythonPython3.1.1—
PythonPython3.1.2—
PythonPython3.1.3—
PythonPython3.1.4—
PythonPython3.1.5—
PythonPython3.2—
PythonPython3.2.0—
PythonPython3.2.1—
PythonPython3.2.2—
PythonPython3.2.3—
PythonPython3.2.4—
PythonPython3.2.5—
PythonPython3.2.2150—
PythonPython3.3—
PythonPython3.3.0—
PythonPython3.3.1—
PythonPython3.3.2—
PythonPython3.3.3—
PythonPython3.3.4—
PythonPython3.3.5—

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2013-7040?
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.
How severe is CVE-2013-7040?
Severity scoring for CVE-2013-7040 is pending analysis. The EPSS model estimates a 3.26% probability of exploitation in the next 30 days.
How do I fix CVE-2013-7040?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2013

View all 2013CVEs →

Are you affected by CVE-2013-7040?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST