CVE-2013-2099

UnknownEPSS 4.86%

Last modified

CVE-2013-2099 is a vulnerability of currently unknown severity. Algorithmic complexity vulnerability in the ssl.match_hostname function in Python 3.2.x, 3.3.x, and earlier, and unspecified versions of python-backports-ssl_match_hostname as used for older Python versions, allows remote attackers to cause a denial of service (CPU consumption) via multiple wildcard characters in the common name in a certificate.. EPSS estimates a 4.86% chance of exploitation in the next 30 days.

Description

Algorithmic complexity vulnerability in the ssl.match_hostname function in Python 3.2.x, 3.3.x, and earlier, and unspecified versions of python-backports-ssl_match_hostname as used for older Python versions, allows remote attackers to cause a denial of service (CPU consumption) via multiple wildcard characters in the common name in a certificate.

Metrics

EPSS Probability
4.86%

90.9th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
PythonPython3.2.0
PythonPython3.2.1
PythonPython3.2.2
PythonPython3.2.3
PythonPython3.2.4
PythonPython3.2.5
PythonPython3.3.0
PythonPython3.3.1
PythonPython3.3.2
CanonicalUbuntu Linux12.04
CanonicalUbuntu Linux12.10
CanonicalUbuntu Linux13.04

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2013-2099?
Algorithmic complexity vulnerability in the ssl.match_hostname function in Python 3.2.x, 3.3.x, and earlier, and unspecified versions of python-backports-ssl_match_hostname as used for older Python versions, allows remote attackers to cause a denial of service (CPU consumption) via multiple wildcard characters in the common name in a certificate.
How severe is CVE-2013-2099?
Severity scoring for CVE-2013-2099 is pending analysis. The EPSS model estimates a 4.86% probability of exploitation in the next 30 days.
How do I fix CVE-2013-2099?
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.

Are you affected by CVE-2013-2099?

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

Scan your code now

Source: NVD / NIST