CVE-2009-2510: Medium severity microsoft windows 2000 vulnerability

Published Oct 14, 2009
·
Updated

The CryptoAPI component in Microsoft Windows 2000 SP4, Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista Gold, SP1, and SP2, Windows Server 2008 Gold, SP2, and R2, and Windows 7, as used by Internet Explorer and other applications, does not properly handle a '\0' character in a domain name in the subject's Common Name (CN) field of an X.509 certificate, which allows man-in-the-middle attackers to spoof arbitrary SSL servers via a crafted certificate issued by a legitimate Certification Authority, aka "Null Truncation in X.509 Common Name Vulnerability," a related issue to CVE-2009-2408.

Affected Software

22 affected components
Microsoft Windows 2000=sp4
Microsoft Windows 2003 Server=sp2
Microsoft Windows 2003 Server=sp2
Microsoft Windows 2003 Server=sp2
Microsoft Windows 7
Microsoft Windows Server 2008
Microsoft Windows Server 2008
Microsoft Windows Server 2008
Microsoft Windows Server 2008=r2
Microsoft Windows Server 2008=r2
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2008=sp2
Microsoft Windows Vista
Microsoft Windows Vista
Microsoft Windows Vista=sp1
Microsoft Windows Vista=sp2
Microsoft Windows XP=sp2
Microsoft Windows XP=sp3
Microsoft Windows XP=sp2
Microsoft Windows Vista=sp2
Microsoft Windows Vista=sp1

Event History

Oct 14, 2009
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2009-2510?

CVE-2009-2510 has a moderate severity rating due to the potential for security vulnerabilities in Microsoft CryptoAPI.

2

What systems are affected by CVE-2009-2510?

CVE-2009-2510 affects multiple Microsoft Windows operating systems including Windows 2000 SP4, XP SP2/SP3, Server 2003 SP2, Vista, Server 2008, and Windows 7.

3

How do I fix CVE-2009-2510?

To fix CVE-2009-2510, users should apply the latest security updates provided by Microsoft for their affected Windows version.

4

What are the potential risks of CVE-2009-2510?

The risks of CVE-2009-2510 include the possibility of remote code execution and unauthorized access to sensitive information.

5

Is there a workaround for CVE-2009-2510?

There are no documented workarounds for CVE-2009-2510; users are advised to update their systems to mitigate the vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203