CVE-2005-2119

NONECVSS 0.0Weaponized
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 39%CVSS: Exploit: NoneExposed: 0

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

The MIDL_user_allocate function in the Microsoft Distributed Transaction Coordinator (MSDTC) proxy (MSDTCPRX.DLL) allocates a 4K page of memory regardless of the required size, which allows attackers to overwrite arbitrary memory locations using an incorrect size value that is provided to the NdrAllocate function, which writes management data to memory outside of the allocated buffer.

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

Published

October 12, 2005

Last Modified

April 16, 2026

Data Freshness Timeline

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

Publicly available exploits

(2 references)

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

  • Exploit-DBEDB-1352✓ verified
    First seen Dec 1, 2005

    Microsoft Windows - DTC Remote (MS05-051) (2)

    Open source ↗
  • Exploit-DBEDB-1341✓ verified
    First seen Nov 27, 2005

    Microsoft Windows - MSDTC Service Remote Memory Modification (PoC) (MS05-051)

    Open source ↗

Frequently asked(4)

What is CVE-2005-2119?
CVE-2005-2119 is a none vulnerability published on October 12, 2005. The MIDLuserallocate function in the Microsoft Distributed Transaction Coordinator (MSDTC) proxy (MSDTCPRX.DLL) allocates a 4K page of memory regardless of the required size, which allows attackers to overwrite arbitrary memory locations using an incorrect size value that is provided to the…
When was CVE-2005-2119 disclosed?
CVE-2005-2119 was first published in the National Vulnerability Database on October 12, 2005, with the most recent update on April 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-2119 actively exploited?
CVE-2005-2119 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2005-2119?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2005-2119, 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-2119

Explore →

Is Your Infrastructure Affected by CVE-2005-2119?

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