CVE-2004-1013

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.8% 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: 6%CVSS v2: 10.0Exploit: None knownExposed: 0

A fix is available — apply it.

The argument parser of the FETCH command in Cyrus IMAP Server 2.2.x through 2.2.8 allows remote authenticated users to execute arbitrary code via certain commands such as (1) "body[p", (2) "binary[p", or (3) "binary[p") that cause an index increment error that leads to an out-of-bounds memory corruption.

CVSS v2.0 (legacy)
10.0HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
10.0(low)
EG Risk
52(Track)
EG Risk 52/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
6%
EPSS %ILE
93%
KEV
Not listed

Published

January 10, 2005

Last Modified

June 16, 2026

References (18)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntucyrus21-imapd () @ warty2026-05-31ubuntu

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
cyrus-imapd—1.5.19-20—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
cyrus-imapd—1.5.19-20—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
cyrus-imapd—1.5.19-20—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
cyrus-imapd—1.5.19-20—
Debian:3.0(1)
PackageVulnerable rangeFixed inDependents
cyrus21-imapd—1.5.19-9.2—

All Vendor Advisories

(1)

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

Frequently asked(4)

What is CVE-2004-1013?
CVE-2004-1013 is a high vulnerability published on January 10, 2005. The argument parser of the FETCH command in Cyrus IMAP Server 2.2.x through 2.2.8 allows remote authenticated users to execute arbitrary code via certain commands such as (1) "body[p", (2) "binary[p", or (3) "binary[p") that cause an index increment error that leads to an out-of-bounds memory…
When was CVE-2004-1013 disclosed?
CVE-2004-1013 was first published in the National Vulnerability Database on January 10, 2005, 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-1013 actively exploited?
CVE-2004-1013 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6% probability of exploitation in the next 30 days, which ranks it in the top 7.4% of all scored CVEs.
How do I remediate CVE-2004-1013?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2004-1013, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2004-1013

Explore →

Is Your Infrastructure Affected by CVE-2004-1013?

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

Start Free Scan →Browse All CVEs