CVE-2013-2099
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
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Python | Python | 3.2.0 |
| Python | Python | 3.2.1 |
| Python | Python | 3.2.2 |
| Python | Python | 3.2.3 |
| Python | Python | 3.2.4 |
| Python | Python | 3.2.5 |
| Python | Python | 3.3.0 |
| Python | Python | 3.3.1 |
| Python | Python | 3.3.2 |
| Canonical | Ubuntu Linux | 12.04 |
| Canonical | Ubuntu Linux | 12.10 |
| Canonical | Ubuntu Linux | 13.04 |
References
- http://secunia.com/advisories/55107Vendor Advisory
- http://secunia.com/advisories/55116Vendor Advisory
- http://secunia.com/advisories/55107Vendor Advisory
- http://secunia.com/advisories/55116Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2013-2099?
How severe is CVE-2013-2099?
How do I fix CVE-2013-2099?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2013
- CVE-2013-2093Dolibarr ERP/CRM 3.3.1 does not properly validate user input…9.8
- CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in th…8.4
- CVE-2013-2095rubygem-openshift-origin-controller: API can be used to crea…9.8
- CVE-2013-2096OpenStack Compute (Nova) Folsom, Grizzly, and Havana does no…
- CVE-2013-2097ZPanel through 10.1.0 has Remote Command Execution7.8
- CVE-2013-2098Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultI…
- CVE-2013-2100The urlopen function in pym/portage/util/_urlopen.py in Gent…
- CVE-2013-2101Katello has multiple XSS issues in various entities5.4
- CVE-2013-2102The default configuration of Red Hat JBoss Portal before 6.1…
- CVE-2013-2103OpenShift cartridge allows remote URL retrieval8.1
- CVE-2013-2104python-keystoneclient before 0.2.4, as used in OpenStack Key…
- CVE-2013-2105The Show In Browser (show_in_browser) gem 0.0.3 for Ruby all…
Are you affected by CVE-2013-2099?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST