CVE-2007-0042

What it is

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."

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure.

Exploit odds

76.2% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2007-07-10 22:30 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 22:34 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 76.2% in the next 30 days (EPSS).
• Severity: 7.8 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2007-07-10 22:30 UTC

Last modified

2026-06-16 22:34 UTC

Exploit probability

76.2% · EPSS, next 30 days

Weakness

CWE-200 · Information exposure

Record status

Modified

Affected

• Microsoft .net Framework 1.0
• Microsoft .net Framework 1.1
• Microsoft .net Framework 2.0

Attack profile CVSS 2.0 · 7.8

Attack vector

Network

Complexity

Low

Authentication

None

Confidentiality

Complete

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2007-0042.md and follow it. Check whether this project is affected by CVE-2007-0042. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge