LiveActive security incident?Get immediate response
CVE Record

CVE-2010-2567: The RPC client implementation in Microsoft Windows XP SP2 and SP3 and Server 2003 SP2 does not properly all...

The RPC client implementation in Microsoft Windows XP SP2 and SP3 and Server 2003 SP2 does not properly allocate memory during the parsing of responses, which allows remote RPC servers and man-in-the-middle attackers to execute arbitrary code via a malformed response, aka "RPC Memory Corruption Vulnerability."

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's Takehigh

Analyst readout for executives and security teams

Plain-English summary

This is a legacy Microsoft Windows RPC client memory corruption flaw. A malicious or intercepted RPC server response could run code on affected Windows XP or Server 2003 systems. It matters mainly where obsolete Windows remains in operational networks. The provided sources do not show current active exploitation.

Executive priority

Treat this as a legacy-system risk. It should not create urgency for modern Windows fleets based on the provided evidence, but any remaining XP or Server 2003 assets warrant priority remediation because the vulnerability can allow code execution.

Technical view

CVE-2010-2567 affects the RPC client implementation in Windows XP SP2/SP3 and Windows Server 2003 SP2. Improper memory allocation while parsing RPC responses can allow arbitrary code execution from a malformed response delivered by a remote RPC server or a man-in-the-middle attacker.

Likely exposure

Exposure is most likely in legacy environments still running Windows XP SP2/SP3 or Windows Server 2003 SP2. The source bundle does not identify newer Windows versions, specific applications, or third-party products as affected.

Exploitation context

The CVE describes remote code execution through malformed RPC responses. KEV status is false, and the provided sources do not document active exploitation. Risk depends on whether affected systems contact untrusted or interceptable RPC servers.

Researcher notes

The bundle provides a CVE description and vendor advisory reference but no CVSS, CWE, proof of exploitation, or detailed patch metadata. Avoid broad product assumptions. Validate exposure through OS inventory, MS10-066 applicability, and the OVAL definition.

Mitigation direction

  • Review Microsoft MS10-066 guidance for the official security update and applicability.
  • Identify and retire remaining Windows XP and Server 2003 systems where possible.
  • Restrict legacy hosts from untrusted RPC paths and unnecessary network access.
  • Prioritize compensating controls if affected systems cannot be patched or replaced.

Validation and detection

  • Inventory endpoints and servers for Windows XP SP2/SP3 and Server 2003 SP2.
  • Check patch management records against Microsoft MS10-066 applicability.
  • Use the referenced OVAL definition where supported by your scanner.
  • Review network paths where legacy systems initiate RPC client connections.
Prepared
Confidence
medium
Sources
4

Public sources used

Based on public source material and reviewed before publication.

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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2010-2567 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
3Source 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.