First published: Wed Jan 09 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."
Credit: secure@microsoft.com
Affected Software | Affected Version | How to fix |
---|---|---|
All of | ||
Microsoft .NET Framework 4 | =2.0-sp2 | |
Any of | ||
Microsoft Windows Server | =sp2 | |
Microsoft Windows Server | =sp2 | |
Microsoft Windows Server | =sp2 | |
Microsoft Windows Server | =sp2 | |
Microsoft Windows Vista | =sp2 | |
Microsoft Windows Vista | =sp2 | |
Microsoft Windows XP | =sp3 | |
Microsoft Windows XP | =sp2 | |
All of | ||
Microsoft .NET Framework 4 | =4.0 | |
Any of | ||
Microsoft Windows 7 | ||
Microsoft Windows 7 | =sp1 | |
Microsoft Windows 7 | =sp1 | |
Microsoft Windows Server | =sp2 | |
Microsoft Windows Server | =r2 | |
Microsoft Windows Server | =r2 | |
Microsoft Windows Server | =sp2 | |
Microsoft Windows Server | =sp2 | |
Microsoft Windows Server | =sp2 | |
Microsoft Windows Vista | =sp2 | |
Microsoft Windows Vista | =sp2 | |
Microsoft Windows XP | =sp3 | |
Microsoft Windows XP | =sp2 | |
All of | ||
Microsoft .NET Framework 4 | =3.5 | |
Any of | ||
Microsoft Windows 8.0 | ||
Microsoft Windows 8.0 | ||
Microsoft Windows Server | ||
All of | ||
Microsoft .NET Framework 4 | =3.5.1 | |
Any of | ||
Microsoft Windows 7 | ||
Microsoft Windows 7 | =sp1 | |
Microsoft Windows 7 | =sp1 | |
Microsoft Windows Server | =r2 | |
Microsoft Windows Server | =r2 | |
All of | ||
Microsoft .NET Framework 4 | =4.5 | |
Any of | ||
Microsoft Windows 7 | =sp1 | |
Microsoft Windows 7 | =sp1 | |
Microsoft Windows 8.0 | ||
Microsoft Windows 8.0 | ||
Microsoft Windows RT | ||
Microsoft Windows Server | ||
Microsoft Windows Vista | =sp2 | |
Microsoft Windows Vista | =sp2 | |
Microsoft .NET Framework 4 | =2.0-sp2 | |
Microsoft Windows Server | =sp2 | |
Microsoft Windows Server | =sp2 | |
Microsoft Windows Server | =sp2 | |
Microsoft Windows Server | =sp2 | |
Microsoft Windows Vista | =sp2 | |
Microsoft Windows Vista | =sp2 | |
Microsoft Windows XP | =sp3 | |
Microsoft Windows XP | =sp2 | |
Microsoft .NET Framework 4 | =4.0 | |
Microsoft Windows 7 | ||
Microsoft Windows 7 | =sp1 | |
Microsoft Windows 7 | =sp1 | |
Microsoft Windows Server | =r2 | |
Microsoft Windows Server | =r2 | |
Microsoft .NET Framework 4 | =3.5 | |
Microsoft Windows 8.0 | ||
Microsoft Windows 8.0 | ||
Microsoft Windows Server | ||
Microsoft .NET Framework 4 | =3.5.1 | |
Microsoft .NET Framework 4 | =4.5 | |
Microsoft Windows RT |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2013-0003 is classified as critical due to its potential to allow remote code execution.
To fix CVE-2013-0003, apply the relevant Microsoft security updates or patches provided for the affected .NET Framework versions.
CVE-2013-0003 affects .NET Framework versions 2.0 SP2, 3.0 SP2, 3.5, 3.5.1, 4, and 4.5.
Yes, CVE-2013-0003 can be exploited remotely through crafted applications like XAML browser applications.
CVE-2013-0003 can facilitate attacks that lead to arbitrary code execution on the affected systems.