CVE-2005-0012

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 3.5% 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
7.5EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3.5%CVSS v2: 7.5Exploit: None knownExposed services: Not assessed

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

Format string vulnerability in the a_Interface_msg function in Dillo before 0.8.3-r4 allows remote attackers to execute arbitrary code via format string specifiers in a web page.

CVSS v2.0 (legacy)
7.5HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.5HIGHlow confidence
EG Risk
40
EG Risk 40/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%
Exploitation3% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
3.5%
EPSS %ILE
88th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Track* or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

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

May 2, 2005

Last Modified

June 16, 2026

References (10)

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
dillo—0.8.3-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
dillo—0.8.3-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
dillo—0.8.3-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
dillo—0.8.3-1—

Data Freshness Timeline

(refreshed 1× in last 7d / 9× 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:42 UTCEG score recompute
  2. 2026-09-19 10:00 UTCOSV refresh
  3. 2026-09-18 19:20 UTCEPSS rescore
  4. 2026-09-17 19:20 UTCEPSS rescore
  5. 2026-09-17 19:20 UTCEPSS rescore
  6. 2026-09-12 14:54 UTCEPSS rescore
  7. 2026-09-10 09:23 UTCEPSS rescore
  8. 2026-09-04 04:59 UTCEPSS rescore
  9. 2026-08-31 13:34 UTCOSV refresh
  10. 2026-08-14 18:54 UTCOSV refresh
  11. 2026-08-08 16:30 UTCEPSS rescore
  12. 2026-08-05 19:11 UTCEPSS rescore
  13. 2026-07-30 07:24 UTCOSV refresh
  14. 2026-07-26 13:25 UTCEG score recompute▲ 7.50
  15. 2026-07-25 14:11 UTCEPSS rescore
  16. 2026-07-24 14:11 UTCEPSS rescore
  17. 2026-07-23 00:47 UTCEG score recompute
  18. 2026-07-23 00:27 UTCEG score recompute
  19. 2026-07-22 23:51 UTCEG score recompute
  20. 2026-07-22 21:31 UTCEG score recompute
  21. 2026-07-18 09:59 UTCEPSS rescore
  22. 2026-07-18 09:59 UTCEPSS rescore
  23. 2026-07-15 16:53 UTCEPSS rescore
  24. 2026-07-15 01:55 UTCEPSS rescore
  25. 2026-07-15 01:55 UTCEPSS rescore
Show 19 more
  1. 2026-07-13 22:24 UTCEPSS rescore
  2. 2026-07-13 06:07 UTCEPSS rescore
  3. 2026-07-13 06:07 UTCEPSS rescore
  4. 2026-07-12 16:37 UTCOSV refresh
  5. 2026-07-11 08:22 UTCEPSS rescore
  6. 2026-07-11 08:22 UTCEPSS rescore
  7. 2026-07-08 15:09 UTCEPSS rescore
  8. 2026-07-02 14:00 UTCEPSS rescore
  9. 2026-07-01 15:01 UTCEPSS rescore
  10. 2026-06-29 14:02 UTCEPSS rescore
  11. 2026-06-29 14:02 UTCEPSS rescore
  12. 2026-06-28 04:52 UTCEPSS rescore
  13. 2026-06-27 03:04 UTCEPSS rescore
  14. 2026-06-25 13:46 UTCEPSS rescore
  15. 2026-06-24 14:01 UTCEPSS rescore
  16. 2026-06-23 22:00 UTCEG score recompute
  17. 2026-06-23 21:59 UTCGHSA enrichment
  18. 2026-06-23 21:59 UTCOSV refresh
  19. 2026-06-23 21:58 UTCNVD updatefirst tracked

Related CVEs(same product)

Same product

1 shown

Debian:11:dillo

Frequently asked(4)

What is CVE-2005-0012?
CVE-2005-0012 is a high vulnerability published on May 2, 2005. Format string vulnerability in the aInterfacemsg function in Dillo before 0.8.3-r4 allows remote attackers to execute arbitrary code via format string specifiers in a web page.
When was CVE-2005-0012 disclosed?
CVE-2005-0012 was first published on May 2, 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-2005-0012 actively exploited?
CVE-2005-0012 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.5% probability of exploitation in the next 30 days (88th percentile of EPSS-scored CVEs).
How do I remediate CVE-2005-0012?
No fix for CVE-2005-0012 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2005-0012

Explore →

Is Your Infrastructure Affected by CVE-2005-0012?

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

Book a Demo →Browse All CVEs