CVE-2013-2099

MEDIUMCVSS v2 · 4.34.3—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 4.3 — v2 rates that MEDIUM (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:M/Au:N/C:N/I:N/A:P. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 4.9% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Trending — 3 sources updated this week
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 4.9%CVSS v2: 4.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v2.0 (legacy)
4.3MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
4.3MEDIUMlow confidence
EG Risk
26
EG Risk 26/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity43% × 45%
Exploitation5% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
4.9%
EPSS %ILE
91st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 9, 2013

Last Modified

April 29, 2026

References (20)

Vendor Advisories for CVE-2013-2099(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3.3-minimal (3.3.1-1ubuntu5.2) @ raring2026-05-28ubuntu
ubuntupython3.2-minimal (3.2.3-6ubuntu3.4) @ quantal2026-05-28ubuntu
ubuntupython2.7-minimal (2.7.3-5ubuntu4.3) @ quantal2026-05-28ubuntu
redhatyaml-cpp-0:0.5.1-7.el7sat2016-07-27redhat
redhatpython27-scipy-0:0.12.1-4.el72016-05-31redhat
redhatpython-urllib3-0:1.5-5.1.2.el62015-01-13redhat
redhatpython-backports-ssl_match_hostname-0:3.4.0.2-1.el62014-10-22redhat
redhatrhsc-branding-rhs-0:2.1.5-2.0.el6rhs2014-09-18redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(17 across 5 ecosystems)
Debian:11(5)
PackageVulnerable rangeFixed inDependents
bzr—2.6.0~bzr6574-1—
linkchecker—8.5-1—
python2.7—2.7.5-5—
python-tornado—2.4.1-3—
python-urllib3—1.6-2—
Debian:12(4)
PackageVulnerable rangeFixed inDependents
bzr—2.6.0~bzr6574-1—
linkchecker—8.5-1—
python-tornado—2.4.1-3—
python-urllib3—1.6-2—
Debian:13(4)
PackageVulnerable rangeFixed inDependents
bzr—2.6.0~bzr6574-1—
linkchecker—8.5-1—
python-tornado—2.4.1-3—
python-urllib3—1.6-2—
Debian:14(3)
PackageVulnerable rangeFixed inDependents
linkchecker—8.5-1—
python-tornado—2.4.1-3—
python-urllib3—1.6-2—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
bzr2.6.0~bzr6526-12.6.0~bzr6526-1+deb7u1—

Additional Vendor Advisories

(6)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 3× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 143 total refreshes for this CVE.

  1. 2026-09-30 14:58 UTCEPSS rescore
  2. 2026-09-30 01:40 UTCOSV refresh
  3. 2026-09-29 20:15 UTCEG score recompute
  4. 2026-09-27 13:39 UTCEPSS rescore
  5. 2026-09-26 15:52 UTCEPSS rescore
  6. 2026-09-24 13:57 UTCEPSS rescore
  7. 2026-09-18 19:21 UTCEPSS rescore
  8. 2026-09-15 03:04 UTCEPSS rescore
  9. 2026-09-12 14:55 UTCEPSS rescore
  10. 2026-09-11 09:30 UTCEPSS rescore
  11. 2026-09-11 02:23 UTCOSV refresh
  12. 2026-09-07 15:56 UTCEPSS rescore
  13. 2026-09-06 13:42 UTCEPSS rescore
  14. 2026-09-05 15:22 UTCEPSS rescore
  15. 2026-09-04 13:55 UTCEPSS rescore
  16. 2026-09-02 14:06 UTCEPSS rescore
  17. 2026-09-01 13:47 UTCEPSS rescore
  18. 2026-08-27 14:20 UTCEPSS rescore
  19. 2026-08-26 14:40 UTCEPSS rescore
  20. 2026-08-25 13:43 UTCEPSS rescore
  21. 2026-08-24 07:23 UTCEPSS rescore
  22. 2026-08-23 16:22 UTCOSV refresh
  23. 2026-08-21 23:44 UTCEPSS rescore
  24. 2026-08-20 22:50 UTCEPSS rescore
  25. 2026-08-19 16:59 UTCEPSS rescore
Show 75 more
  1. 2026-08-18 13:42 UTCEPSS rescore
  2. 2026-08-16 02:09 UTCEPSS rescore
  3. 2026-08-15 01:25 UTCEPSS rescore
  4. 2026-08-12 13:45 UTCEPSS rescore
  5. 2026-08-09 13:42 UTCEPSS rescore
  6. 2026-08-08 16:31 UTCEPSS rescore
  7. 2026-08-07 17:19 UTCOSV refresh
  8. 2026-08-07 16:21 UTCEPSS rescore
  9. 2026-08-06 13:42 UTCEPSS rescore
  10. 2026-08-05 19:12 UTCEPSS rescore
  11. 2026-08-04 15:04 UTCEPSS rescore
  12. 2026-08-02 02:22 UTCEPSS rescore
  13. 2026-07-30 01:26 UTCEPSS rescore
  14. 2026-07-28 15:31 UTCEPSS rescore
  15. 2026-07-26 13:47 UTCEG score recompute▲ 4.30
  16. 2026-07-25 14:12 UTCEPSS rescore
  17. 2026-07-23 14:14 UTCEPSS rescore
  18. 2026-07-23 01:09 UTCEG score recompute
  19. 2026-07-23 00:13 UTCEG score recompute
  20. 2026-07-22 21:51 UTCEG score recompute
  21. 2026-07-22 14:04 UTCEPSS rescore
  22. 2026-07-22 14:04 UTCEPSS rescore
  23. 2026-07-22 10:07 UTCOSV refresh
  24. 2026-07-21 15:21 UTCEPSS rescore
  25. 2026-07-20 17:03 UTCEPSS rescore
  26. 2026-07-20 17:03 UTCEPSS rescore
  27. 2026-07-19 14:27 UTCEPSS rescore
  28. 2026-07-19 14:27 UTCEPSS rescore
  29. 2026-07-19 02:25 UTCEPSS rescore
  30. 2026-07-19 02:25 UTCEPSS rescore
  31. 2026-07-18 10:00 UTCEPSS rescore
  32. 2026-07-16 16:58 UTCEPSS rescore
  33. 2026-07-15 16:54 UTCEPSS rescore
  34. 2026-07-15 16:54 UTCEPSS rescore
  35. 2026-07-15 01:56 UTCEPSS rescore
  36. 2026-07-13 22:26 UTCEPSS rescore
  37. 2026-07-13 06:08 UTCEPSS rescore
  38. 2026-07-11 08:23 UTCEPSS rescore
  39. 2026-07-09 19:05 UTCEPSS rescore
  40. 2026-07-08 15:10 UTCEPSS rescore
  41. 2026-07-06 02:19 UTCEPSS rescore
  42. 2026-07-06 02:19 UTCEPSS rescore
  43. 2026-07-05 05:21 UTCOSV refresh
  44. 2026-07-05 02:26 UTCEPSS rescore
  45. 2026-07-04 06:27 UTCEPSS rescore
  46. 2026-07-01 15:02 UTCEPSS rescore
  47. 2026-06-30 23:19 UTCEPSS rescore
  48. 2026-06-30 23:19 UTCEPSS rescore
  49. 2026-06-29 14:02 UTCEPSS rescore
  50. 2026-06-28 14:03 UTCEPSS rescore
  51. 2026-06-28 04:53 UTCEPSS rescore
  52. 2026-06-28 04:53 UTCEPSS rescore
  53. 2026-06-27 03:05 UTCEPSS rescore
  54. 2026-06-25 13:46 UTCEPSS rescore
  55. 2026-06-24 14:02 UTCEPSS rescore
  56. 2026-06-24 14:02 UTCEPSS rescore
  57. 2026-06-23 21:30 UTCEPSS rescore
  58. 2026-06-21 14:53 UTCEPSS rescore
  59. 2026-06-21 01:57 UTCEPSS rescore
  60. 2026-06-21 01:56 UTCEPSS rescore
  61. 2026-06-19 19:23 UTCEPSS rescore
  62. 2026-06-19 19:22 UTCEPSS rescore
  63. 2026-06-18 17:49 UTCEPSS rescore
  64. 2026-06-18 17:49 UTCEPSS rescore
  65. 2026-06-17 17:49 UTCEPSS rescore
  66. 2026-06-17 17:49 UTCEPSS rescore
  67. 2026-06-16 17:49 UTCEPSS rescore
  68. 2026-06-16 17:49 UTCEPSS rescore
  69. 2026-06-16 16:44 UTCOSV refresh
  70. 2026-06-15 17:44 UTCEPSS rescore
  71. 2026-06-14 23:14 UTCEPSS rescore
  72. 2026-06-13 22:57 UTCEPSS rescore
  73. 2026-06-12 23:08 UTCEPSS rescore
  74. 2026-06-11 13:56 UTCEPSS rescore
  75. 2026-06-10 13:18 UTCEPSS rescore

Related CVEs(same product + same vendor)

Frequently asked(4)

What is CVE-2013-2099?
CVE-2013-2099 is a medium vulnerability published on October 9, 2013. Algorithmic complexity vulnerability in the ssl.matchhostname function in Python 3.2.x, 3.3.x, and earlier, and unspecified versions of python-backports-sslmatch_hostname as used for older Python versions, allows remote attackers to cause a denial of service (CPU consumption) via multiple wildcard…
When was CVE-2013-2099 disclosed?
CVE-2013-2099 was first published on October 9, 2013, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-2099 actively exploited?
CVE-2013-2099 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.9% probability of exploitation in the next 30 days (91st percentile of EPSS-scored CVEs).
How do I remediate CVE-2013-2099?
A fix for CVE-2013-2099 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2013-2099 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2013-2099

Explore →

Is Your Infrastructure Affected by CVE-2013-2099?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs