CVE-2009-4484

HIGHCVSS v2 · 7.57.5—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.5 — v2 rates that HIGH (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:L/Au:N/C:P/I:P/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 69.6% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: epss, nvd_v2
Weaponized
7.5EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 70%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 70%CVSS v2: 7.5Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed services: Not assessed

A fix is available — apply it.

Multiple stack-based buffer overflows in the CertDecoder::GetName function in src/asn.cpp in TaoCrypt in yaSSL before 1.9.9, as used in mysqld in MySQL 5.0.x before 5.0.90, MySQL 5.1.x before 5.1.43, MySQL 5.5.x through 5.5.0-m2, and other products, allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption and daemon crash) by establishing an SSL connection and sending an X.509 client certificate with a crafted name field, as demonstrated by mysql_overflow1.py and the vd_mysql5 module in VulnDisco Pack Professional 8.11. NOTE: this was originally reported for MySQL 5.0.51a.

CVSS v2.0 (legacy)
7.5HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.5HIGHlow confidence
EG Risk
66
EG Risk 66/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
Severity75% × 45%
Exploitation70% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track or Track* at medium and Track* or Attend at high mission impact.
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
70%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low, Track or Track* at medium and Track* or Attend at high mission impact.

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

Exploitation public PoC (EG-KEV: weaponized) · 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

December 30, 2009

Last Modified

April 23, 2026

References (72)

Vendor Advisories for CVE-2009-4484(1)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntumysql-server-5.1 (5.1.61-0ubuntu0.11.10.1) @ oneiric2026-05-29ubuntu
ubuntumysql-server-5.0 (5.1.30really5.0.75-0ubuntu10.3) @ jaunty2026-05-29ubuntu

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

(2 across 2 ecosystems)
Debian:4.0(1)
PackageVulnerable rangeFix by version rangeDependents
mysql-dfsg-5.05.0.32-7etch1 ... 5.0.32-7etch8 (10 versions)
  • every version up to 5.0.32-7etch12: fixed in 5.0.32-7etch12
—
Debian:5.0(1)
PackageVulnerable rangeFix by version rangeDependents
mysql-dfsg-5.05.0.51a-23 ... 5.0.51a-24~bpo40+1 (8 versions)
  • every version up to 5.0.51a-24+lenny3: fixed in 5.0.51a-24+lenny3
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

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 6× 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.

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

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Metasploit module) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-16850✓ verified
    First seen Apr 30, 2010

    MySQL - yaSSL CertDecoder::GetName Buffer Overflow (Metasploit)

    Open source ↗
  • Metasploitexploit/linux/mysql/mysql_yassl_getname✓ verified
    First seen Jan 25, 2010

    MySQL yaSSL CertDecoder::GetName Buffer Overflow

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(4)

What is CVE-2009-4484?
CVE-2009-4484 is a high vulnerability published on December 30, 2009. Multiple stack-based buffer overflows in the CertDecoder::GetName function in src/asn.cpp in TaoCrypt in yaSSL before 1.9.9, as used in mysqld in MySQL 5.0.x before 5.0.90, MySQL 5.1.x before 5.1.43, MySQL 5.5.x through 5.5.0-m2, and other products, allow remote attackers to execute arbitrary code…
When was CVE-2009-4484 disclosed?
CVE-2009-4484 was first published on December 30, 2009, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2009-4484 actively exploited?
CVE-2009-4484 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 70% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
How do I remediate CVE-2009-4484?
A fix for CVE-2009-4484 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2009-4484 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-2009-4484

Explore →

Is Your Infrastructure Affected by CVE-2009-4484?

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

Book a Demo →Browse All CVEs