LiveActive security incident?Get immediate response
CVE Record

CVE-2005-2119: The MIDL_user_allocate function in the Microsoft Distributed Transaction Coordinator (MSDTC) proxy (MSDTCPR...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2005-2119 is a memory corruption flaw in Microsoft MSDTC proxy handling. The component can allocate too little memory and then write outside that buffer, creating a path to corrupt arbitrary memory. The bundle does not identify affected versions, business prevalence, or active exploitation evidence. Exposure should be assessed on systems running Microsoft Distributed Transaction Coordinator components covered by MS05-051. The provided CVE record lists affected vendor/product as n/a, so asset teams must use Microsoft guidance and OVAL checks rather than the bundle alone. Treat as a legacy Microsoft infrastructure risk requiring inventory and patch verification. Priority rises if MSDTC exists on unsupported, externally reachable, or business-critical Windows systems. Current exploitation urgency is not proven by the supplied sources. Mitigation focus: Review Microsoft MS05-051 for affected platforms and required updates.; Apply the applicable Microsoft security update where systems match vendor criteria.; Identify systems with MSDTC components installed or enabled..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2005-2119 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.