First published: Wed Oct 14 2009(Updated: )
Microsoft .NET Framework 2.0, 2.0 SP1, and 3.5 does not properly enforce a certain type-equality constraint in .NET verifiable code, which allows remote attackers to 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 Type 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-0091 is rated as critical due to its potential to allow remote code execution.
To resolve CVE-2009-0091, you should apply the latest security updates provided by Microsoft for the affected .NET Framework versions.
CVE-2009-0091 affects Microsoft .NET Framework versions 1.0, 1.1, 2.0, 2.0 SP1, 2.0 SP2, 3.5, and various versions of Windows, including Windows 2000, Server 2003, Server 2008, Vista, and XP.
Attackers can exploit CVE-2009-0091 via crafted XAML browser applications (XBAP) or ASP.NET applications that leverage the vulnerability.
While the most effective mitigation for CVE-2009-0091 is to apply the security updates, temporarily restricting access to .NET applications may help reduce the risk until a patch can be applied.