Interpretation conflict in ASP.NET in Microsoft .NET Framework 1.0, 1.1, and 2.0 for Windows 2000, XP, Server 2003…
No fixed version listed yet.Check the vendor advisory. References ↓
The flaw is an interpretation conflict in ASP.NET within Microsoft .NET Framework 1.0, 1.1, and 2.0, where a %00 sequence is treated as a string terminator by POSIX-style functions but as an ordinary data character within .NET strings. An attacker with remote access can send crafted %00 sequences to read configuration files and obtain sensitive information, and may be able to bypass security checks that constrain the final substring of a string.
Official description · CVE.org
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."
- Exploited
- Not confirmed
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Public exploit code (Exploit-DB) was available 4 days before disclosure.
- Public exploit codeExploit-DB4 days before
- Disclosedday 0
What security researchers reported
Not named in any threat report yetAlso mentioned in 1 community threat pulse (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.