CVE-2005-0308

NONECVSS 0.0Weaponized
0.0
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 64%
CISA-KEV: Not listedEPSS: 64%CVSS: —Exploit: NoneExposed: 0

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

Buffer overflow in the wsprintf function in W32Dasm 8.93 and earlier allows remote attackers to execute arbitrary code via a large import or export function name.

CVSS v3
—
EG Score
0.0(none)
EPSS
99.1%
KEV
Not listed

Published

January 24, 2005

Last Modified

June 16, 2026

References (10)

Data Freshness Timeline

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

Publicly available exploits

(2 references)

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

  • Exploit-DBEDB-16645✓ verified
    First seen Sep 25, 2010

    URSoft W32Dasm 8.93 - Disassembler Function Buffer Overflow (Metasploit)

    Open source ↗
  • Metasploitexploit/windows/fileformat/ursoft_w32dasm✓ verified
    First seen Jan 24, 2005

    URSoft W32Dasm Disassembler Function Buffer Overflow

    Open source ↗

Frequently asked(4)

What is CVE-2005-0308?
CVE-2005-0308 is a none vulnerability published on January 24, 2005. Buffer overflow in the wsprintf function in W32Dasm 8.93 and earlier allows remote attackers to execute arbitrary code via a large import or export function name.
When was CVE-2005-0308 disclosed?
CVE-2005-0308 was first published in the National Vulnerability Database on January 24, 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-0308 actively exploited?
CVE-2005-0308 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2005-0308?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2005-0308, 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-2005-0308

Explore →

Is Your Infrastructure Affected by CVE-2005-0308?

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

Start Free Scan →Browse All CVEs