CVE-2003-0780

HIGHCVSS v2 · 9.09.0—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 9.0 — 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:S/C:C/I:C/A:C. 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 78.4% 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
Weaponized
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 78%
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 78%CVSS v2: 9.0Exploit: Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed services: Not assessed

A fix is available — apply it.

Buffer overflow in get_salt_from_password from sql_acl.cc for MySQL 4.0.14 and earlier, and 3.23.x, allows attackers with ALTER TABLE privileges to execute arbitrary code via a long Password field.

CVSS v2.0 (legacy)
9.0HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
9.0HIGHlow confidence
EG Risk
76
EG Risk 76/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
Severity90% × 45%
Exploitation78% × 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
78%
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

September 22, 2003

Last Modified

June 16, 2026

References (22)

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2003-10-09redhat
redhatpatch2003-10-09redhat

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

(1 across 1 ecosystem)
Debian:3.0(1)
PackageVulnerable rangeFixed inDependents
mysql—3.23.49-8.5—

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 1× in last 7d / 3× 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-09-29 02:38 UTCEG score recompute
  2. 2026-09-12 14:54 UTCEPSS rescore
  3. 2026-09-10 09:23 UTCEPSS rescore
  4. 2026-07-26 13:23 UTCEG score recompute▲ 9.00
  5. 2026-07-25 14:11 UTCEPSS rescore
  6. 2026-07-24 14:11 UTCEPSS rescore
  7. 2026-07-23 00:45 UTCEG score recompute
  8. 2026-07-23 00:26 UTCEG score recompute▼ 7.90
  9. 2026-07-22 23:49 UTCEG score recompute▲ 7.90
  10. 2026-07-22 21:30 UTCEG score recompute
  11. 2026-07-20 17:02 UTCEPSS rescore
  12. 2026-07-18 09:59 UTCEPSS rescore
  13. 2026-07-18 09:59 UTCEPSS rescore
  14. 2026-07-16 16:58 UTCEPSS rescore
  15. 2026-07-13 06:07 UTCEPSS rescore
  16. 2026-07-11 08:22 UTCEPSS rescore
  17. 2026-07-11 08:22 UTCEPSS rescore
  18. 2026-07-08 15:09 UTCEPSS rescore
  19. 2026-07-04 06:26 UTCEPSS rescore
  20. 2026-06-28 14:02 UTCEPSS rescore
  21. 2026-06-27 03:04 UTCEPSS rescore
  22. 2026-06-23 21:29 UTCEPSS rescore
  23. 2026-06-21 14:52 UTCEPSS rescore
  24. 2026-06-18 17:49 UTCEPSS rescore
  25. 2026-06-18 17:49 UTCEPSS rescore
Show 30 more
  1. 2026-06-16 17:49 UTCEPSS rescore
  2. 2026-06-16 17:49 UTCEPSS rescore
  3. 2026-06-15 17:43 UTCEPSS rescore
  4. 2026-06-14 23:13 UTCEPSS rescore
  5. 2026-06-14 23:13 UTCEPSS rescore
  6. 2026-06-13 22:56 UTCEPSS rescore
  7. 2026-06-12 23:08 UTCEPSS rescore
  8. 2026-06-11 13:55 UTCEPSS rescore
  9. 2026-06-10 22:13 UTCEPSS rescore
  10. 2026-06-08 14:13 UTCEPSS rescore
  11. 2026-06-07 15:21 UTCEPSS rescore
  12. 2026-06-05 22:43 UTCEPSS rescore
  13. 2026-06-05 22:43 UTCEPSS rescore
  14. 2026-06-05 06:07 UTCEPSS rescore
  15. 2026-06-04 13:09 UTCEPSS rescore
  16. 2026-06-01 13:49 UTCEPSS rescore
  17. 2026-06-01 13:49 UTCEPSS rescore
  18. 2026-05-31 17:16 UTCEG score recompute
  19. 2026-05-31 17:16 UTCVendor advisory
  20. 2026-05-31 17:15 UTCGHSA enrichment
  21. 2026-05-31 00:13 UTCEPSS rescore
  22. 2026-05-31 00:13 UTCEPSS rescore
  23. 2026-05-29 13:40 UTCEPSS rescore
  24. 2026-05-29 13:40 UTCEPSS rescore
  25. 2026-05-27 13:37 UTCEPSS rescore
  26. 2026-05-24 16:42 UTCEPSS rescore
  27. 2026-05-22 21:15 UTCEPSS rescore
  28. 2026-05-20 22:36 UTCEPSS rescore
  29. 2026-05-18 21:29 UTCEPSS rescore
  30. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(2 references)

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

  • Exploit-DBEDB-98✓ verified
    First seen Sep 14, 2003

    MySQL 3.23.x/4.0.x - Remote Buffer Overflow

    Open source ↗
  • Exploit-DBEDB-23138✓ verified
    First seen Sep 10, 2003

    MySQL 3.23.x/4.0.x - Password Handler Buffer Overflow

    Open source ↗

Related CVEs(same product)

Frequently asked(4)

What is CVE-2003-0780?
CVE-2003-0780 is a high vulnerability published on September 22, 2003. Buffer overflow in getsaltfrompassword from sqlacl.cc for MySQL 4.0.14 and earlier, and 3.23.x, allows attackers with ALTER TABLE privileges to execute arbitrary code via a long Password field.
When was CVE-2003-0780 disclosed?
CVE-2003-0780 was first published on September 22, 2003, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2003-0780 actively exploited?
CVE-2003-0780 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 78% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
How do I remediate CVE-2003-0780?
A fix for CVE-2003-0780 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2003-0780

Explore →

Is Your Infrastructure Affected by CVE-2003-0780?

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

Book a Demo →Browse All CVEs