CVE-2004-0413

HIGHCVSS v2 · 10.010.0—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 10.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:N/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 5.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
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 5.9%CVSS v2: 10.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

libsvn_ra_svn in Subversion 1.0.4 trusts the length field of (1) svn://, (2) svn+ssh://, and (3) other svn protocol URL strings, which allows remote attackers to cause a denial of service (memory consumption) and possibly execute arbitrary code via an integer overflow that leads to a heap-based buffer overflow.

CVSS v2.0 (legacy)
10.0HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
10.0HIGHlow confidence
EG Risk
52
EG Risk 52/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
Severity100% × 45%
Exploitation6% × 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
5.9%
EPSS %ILE
92nd
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

August 6, 2004

Last Modified

June 16, 2026

References (16)

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
subversion—
  • every version up to 1.0.5-1: fixed in 1.0.5-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
subversion—
  • every version up to 1.0.5-1: fixed in 1.0.5-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
subversion—
  • every version up to 1.0.5-1: fixed in 1.0.5-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
subversion—
  • every version up to 1.0.5-1: fixed in 1.0.5-1
—

Data Freshness Timeline

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

Related CVEs(same product)

Frequently asked(4)

What is CVE-2004-0413?
CVE-2004-0413 is a high vulnerability published on August 6, 2004. libsvnrasvn in Subversion 1.0.4 trusts the length field of (1) svn://, (2) svn+ssh://, and (3) other svn protocol URL strings, which allows remote attackers to cause a denial of service (memory consumption) and possibly execute arbitrary code via an integer overflow that leads to a heap-based…
When was CVE-2004-0413 disclosed?
CVE-2004-0413 was first published on August 6, 2004, 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-2004-0413 actively exploited?
CVE-2004-0413 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.9% probability of exploitation in the next 30 days (92nd percentile of EPSS-scored CVEs).
How do I remediate CVE-2004-0413?
A fix for CVE-2004-0413 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-2004-0413

Explore →

Is Your Infrastructure Affected by CVE-2004-0413?

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

Book a Demo →Browse All CVEs