First published: Wed Oct 14 2009(Updated: )
Microsoft .NET Framework 1.0 SP3, 1.1 SP1, and 2.0 SP1 does not properly validate .NET verifiable code, which allows remote attackers to obtain unintended access to stack memory, and execute arbitrary code, via (1) a crafted XAML browser application (XBAP), (2) a crafted ASP.NET application, or (3) a crafted .NET Framework application, aka "Microsoft .NET Framework Pointer Verification Vulnerability."
Credit: secure@microsoft.com
Affected Software | Affected Version | How to fix |
---|---|---|
All of | ||
Microsoft Windows 2000 | =sp4 | |
Any of | ||
Microsoft .NET Framework 4 | =1.1-sp1 | |
Microsoft .NET Framework 4 | =2.0-sp1 | |
Microsoft .NET Framework 4 | =2.0-sp2 | |
All of | ||
Any of | ||
Microsoft Windows Server | =sp2 | |
Microsoft Windows Server | ||
Microsoft Windows Server | ||
Microsoft Windows Server | ||
Microsoft Windows Server | =sp2 | |
Microsoft Windows Server | =sp2 | |
Microsoft Windows Server | =sp2 | |
Microsoft Windows Server | =sp2 | |
Any of | ||
Microsoft .NET Framework 4 | =1.1-sp1 | |
Microsoft .NET Framework 4 | =2.0-sp1 | |
Microsoft .NET Framework 4 | =2.0-sp2 | |
Microsoft .NET Framework 4 | =3.5 | |
Microsoft .NET Framework 4 | =3.5-sp1 | |
All of | ||
Any of | ||
Microsoft Windows Vista | ||
Microsoft Windows Vista | ||
Microsoft Windows Vista | =sp1 | |
Microsoft Windows Vista | =sp2 | |
Any of | ||
Microsoft .NET Framework 4 | =1.1-sp1 | |
Microsoft .NET Framework 4 | =2.0 | |
Microsoft .NET Framework 4 | =2.0-sp1 | |
Microsoft .NET Framework 4 | =2.0-sp2 | |
Microsoft .NET Framework 4 | =3.5 | |
Microsoft .NET Framework 4 | =3.5-sp1 | |
All of | ||
Microsoft .NET Framework 4 | =1.1-sp1 | |
Any of | ||
Microsoft Windows 7 | ||
Microsoft Windows Server | =r2 | |
Microsoft Windows Server | =r2 | |
All of | ||
Any of | ||
Microsoft .NET Framework 4 | =1.0-sp3 | |
Microsoft .NET Framework 4 | =1.1-sp1 | |
Microsoft .NET Framework 4 | =2.0-sp1 | |
Microsoft .NET Framework 4 | =2.0-sp2 | |
Microsoft .NET Framework 4 | =3.5 | |
Microsoft .NET Framework 4 | =3.5-sp1 | |
Any of | ||
Microsoft Windows XP | =sp2 | |
Microsoft Windows XP | =sp3 | |
Microsoft Windows XP | =sp2 | |
Microsoft Windows 2000 | =sp4 | |
Microsoft .NET Framework 4 | =1.1-sp1 | |
Microsoft .NET Framework 4 | =2.0-sp1 | |
Microsoft .NET Framework 4 | =2.0-sp2 | |
Microsoft Windows Server | =sp2 | |
Microsoft Windows Server | ||
Microsoft Windows Server | ||
Microsoft Windows Server | ||
Microsoft Windows Server | =sp2 | |
Microsoft Windows Server | =sp2 | |
Microsoft Windows Server | =sp2 | |
Microsoft Windows Server | =sp2 | |
Microsoft .NET Framework 4 | =3.5 | |
Microsoft .NET Framework 4 | =3.5-sp1 | |
Microsoft Windows Vista | ||
Microsoft Windows Vista | ||
Microsoft Windows Vista | =sp1 | |
Microsoft Windows Vista | =sp1 | |
Microsoft Windows Vista | =sp2 | |
Microsoft Windows Vista | =sp2 | |
Microsoft .NET Framework 4 | =2.0 | |
Microsoft Windows 7 | ||
Microsoft Windows Server | =r2 | |
Microsoft Windows Server | =r2 | |
Microsoft .NET Framework 4 | =1.0-sp3 | |
Microsoft Windows XP | =sp2 | |
Microsoft Windows XP | =sp3 | |
Microsoft Windows XP | =sp2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2009-0090 has a critical severity rating due to its potential for remote code execution.
To fix CVE-2009-0090, you should apply the security update released by Microsoft as part of MS09-061.
CVE-2009-0090 affects Microsoft .NET Framework versions 1.0 SP3, 1.1 SP1, 2.0 SP1, and other related versions.
Yes, CVE-2009-0090 can be exploited through crafted XAML browser applications (XBAP) and ASP.NET applications.
CVE-2009-0090 impacts various versions of Microsoft Windows, including Windows 2000, Windows XP, Windows Server 2003, and more.