CVE-2003-0625

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory published 2022-04-29. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 7%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Off-by-one error in certain versions of xfstt allows remote attackers to read potentially sensitive memory via a malformed client request in the connection handshake, which leaks the memory in the server's response.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
93.5%
KEV
Not listed

Published

August 27, 2003

Last Modified

June 16, 2026

Advisory Details (3)

Auto-updated Jun 23, 2026
No patch confirmed yet.
generic

Debian -- The Universal Operating System

http://www.debian.org/security/2003/dsa-360
generic

'[PAPER]: Address relay fingerprinting.' - MARC

http://marc.info/?l=bugtraq&m=105941103709264&w=2

Weakness Classification(1)

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

Data Freshness Timeline

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

Publicly available exploits

(1 reference)

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

  • Exploit-DBEDB-22952✓ verified
    First seen Jul 23, 2003

    xfstt 1.2/1.4 - Memory Disclosure

    Open source ↗

Frequently asked(5)

What is CVE-2003-0625?
CVE-2003-0625 is a high vulnerability published on August 27, 2003. Off-by-one error in certain versions of xfstt allows remote attackers to read potentially sensitive memory via a malformed client request in the connection handshake, which leaks the memory in the server's response.
When was CVE-2003-0625 disclosed?
CVE-2003-0625 was first published in the National Vulnerability Database on August 27, 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-0625 actively exploited?
CVE-2003-0625 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 93.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2003-0625?
CVE-2003-0625 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2003-0625?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2003-0625, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2003-0625

Explore →

Is Your Infrastructure Affected by CVE-2003-0625?

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