First published: Tue Jul 10 2007(Updated: )
Interpretation conflict in ASP.NET in Microsoft .NET Framework 1.0, 1.1, and 2.0 for Windows 2000, XP, Server 2003, and Vista allows remote attackers to access configuration files and obtain sensitive information, and possibly bypass security mechanisms that try to constrain the final substring of a string, via %00 characters, related to use of %00 as a string terminator within POSIX functions but a data character within .NET strings, aka "Null Byte Termination Vulnerability."
Credit: secure@microsoft.com
Affected Software | Affected Version | How to fix |
---|---|---|
Microsoft Windows 2000 | ||
Microsoft Windows Server 2003 | ||
Microsoft Windows Vista | ||
Microsoft Windows XP | ||
Microsoft .NET Framework 4 | =1.0 | |
Microsoft .NET Framework 4 | =1.1 | |
Microsoft .NET Framework 4 | =2.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2007-0042 has a high severity rating due to its potential for unauthorized access to sensitive configuration files.
To fix CVE-2007-0042, update the Microsoft .NET Framework to a version that addresses this vulnerability.
CVE-2007-0042 affects Microsoft .NET Framework versions 1.0, 1.1, and 2.0.
Yes, CVE-2007-0042 can be exploited remotely by attackers targeting vulnerable applications.
CVE-2007-0042 affects systems running Microsoft Windows 2000, XP, Server 2003, and Vista with the vulnerable versions of .NET Framework.