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."
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Link | Tags |
|---|---|
| http://archive.cert.uni-stuttgart.de/bugtraq/2007/07/msg00254.html | vendor advisory |
| https://docs.microsoft.com/en-us/security-updates/securitybulletins/2007/ms07-040 | vendor advisory |
| http://www.vupen.com/english/advisories/2007/2482 | vdb entry |
| https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A2070 | signature vdb entry |
| http://secunia.com/advisories/26003 | third party advisory vendor advisory |
| http://security-assessment.com/files/advisories/2007-07-11_Multiple_.NET_Null_Byte_Injection_Vulnerabilities.pdf | |
| http://www.us-cert.gov/cas/techalerts/TA07-191A.html | third party advisory us government resource |
| http://www.securitytracker.com/id?1018356 | vdb entry |