CVE-2013-0003: Buffer Overflow

Published Jan 9, 2013
·
Updated

Buffer overflow in a System.DirectoryServices.Protocols (S.DS.P) namespace method in Microsoft .NET Framework 2.0 SP2, 3.0 SP2, 3.5, 3.5.1, 4, and 4.5 allows remote attackers to execute arbitrary code via (1) a crafted XAML browser application (XBAP) or (2) a crafted .NET Framework application that leverages a missing array-size check during a memory copy operation, aka "S.DS.P Buffer Overflow Vulnerability."

Affected Software

64 affected components
All of the following
Microsoft .NET Framework=2.0-sp2
Any of the following
Microsoft Windows Server 2003=sp2
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2008=sp2
Microsoft Windows Vista=sp2
Microsoft Windows Vista=sp2
Microsoft Windows XP=sp3
Microsoft Windows XP=sp2
All of the following
Microsoft .NET Framework=4.0
Any of the following
Microsoft Windows 7
Microsoft Windows 7=sp1
Microsoft Windows 7=sp1
Microsoft Windows Server 2003=sp2
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=sp2
Microsoft Windows Vista=sp2
Microsoft Windows XP=sp3
Microsoft Windows XP=sp2
All of the following
Microsoft .NET Framework=3.5
Any of the following
Microsoft Windows 8
Microsoft Windows 8
Microsoft Windows Server 2012
All of the following
Microsoft .NET Framework=3.5.1
Any of the following
Microsoft Windows 7
Microsoft Windows 7=sp1
Microsoft Windows 7=sp1
Microsoft Windows Server 2008=r2
Microsoft Windows Server 2008=r2
All of the following
Microsoft .NET Framework=4.5
Any of the following
Microsoft Windows 7=sp1
Microsoft Windows 7=sp1
Microsoft Windows 8
Microsoft Windows 8
Microsoft Windows RT
Microsoft Windows Server 2012
Microsoft Windows Vista=sp2
Microsoft Windows Vista=sp2
Microsoft .NET Framework=2.0-sp2
Microsoft Windows Server 2003=sp2
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2008=sp2
Microsoft Windows Vista=sp2
Microsoft Windows Vista=sp2
Microsoft Windows XP=sp3
Microsoft Windows XP=sp2
Microsoft .NET Framework=4.0
Microsoft Windows 7
Microsoft Windows 7=sp1
Microsoft Windows 7=sp1
Microsoft Windows Server 2008=r2
Microsoft Windows Server 2008=r2
Microsoft .NET Framework=3.5
Microsoft Windows 8
Microsoft Windows 8
Microsoft Windows Server 2012
Microsoft .NET Framework=3.5.1
Microsoft .NET Framework=4.5
Microsoft Windows RT

Event History

Jan 9, 2013
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2013-0003?

The severity of CVE-2013-0003 is classified as critical due to its potential to allow remote code execution.

2

How do I fix CVE-2013-0003?

To fix CVE-2013-0003, apply the relevant Microsoft security updates or patches provided for the affected .NET Framework versions.

3

Which versions of .NET Framework are affected by CVE-2013-0003?

CVE-2013-0003 affects .NET Framework versions 2.0 SP2, 3.0 SP2, 3.5, 3.5.1, 4, and 4.5.

4

Can CVE-2013-0003 be exploited remotely?

Yes, CVE-2013-0003 can be exploited remotely through crafted applications like XAML browser applications.

5

What types of attacks can CVE-2013-0003 facilitate?

CVE-2013-0003 can facilitate attacks that lead to arbitrary code execution on the affected systems.

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