CVE-2007-0042

HIGHCVSS v2 · 7.87.8—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.8 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:C/I:N/A:N. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 76.2% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: epss, nvd_v2
Weaponized
7.8EG
EchelonGraph verdictMitigate this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 76%
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 76%CVSS v2: 7.8Exploit: Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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

CVSS v2.0 (legacy)
7.8HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.8HIGHlow confidence
EG Risk
70
EG Risk 70/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation76% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track or Track* at medium and Track* or Attend at high mission impact.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
76%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low, Track or Track* at medium and Track* or Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 10, 2007

Last Modified

April 23, 2026

References (16)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 3× in last 7d / 9× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-09 19:59 UTCEPSS rescore
  2. 2026-10-07 23:36 UTCEPSS rescore
  3. 2026-10-05 17:37 UTCEPSS rescore
  4. 2026-09-29 07:37 UTCEG score recompute
  5. 2026-09-18 19:20 UTCEPSS rescore
  6. 2026-09-15 03:04 UTCEPSS rescore
  7. 2026-09-13 16:40 UTCEPSS rescore
  8. 2026-09-12 14:54 UTCEPSS rescore
  9. 2026-09-10 09:24 UTCEPSS rescore
  10. 2026-09-05 15:22 UTCEPSS rescore
  11. 2026-09-04 13:54 UTCEPSS rescore
  12. 2026-08-30 01:14 UTCEPSS rescore
  13. 2026-08-07 16:20 UTCEPSS rescore
  14. 2026-08-06 13:41 UTCEPSS rescore
  15. 2026-08-04 10:28 UTCEPSS rescore
  16. 2026-07-26 13:31 UTCEG score recompute▲ 7.80
  17. 2026-07-25 14:11 UTCEPSS rescore
  18. 2026-07-24 14:11 UTCEPSS rescore
  19. 2026-07-23 00:52 UTCEG score recompute
  20. 2026-07-23 00:31 UTCEG score recompute▼ 7.60
  21. 2026-07-22 23:56 UTCEG score recompute▲ 7.60
  22. 2026-07-22 21:36 UTCEG score recompute
  23. 2026-07-22 14:03 UTCEPSS rescore
  24. 2026-07-21 15:19 UTCEPSS rescore
  25. 2026-07-20 17:02 UTCEPSS rescore
Show 58 more
  1. 2026-07-16 16:58 UTCEPSS rescore
  2. 2026-07-15 16:54 UTCEPSS rescore
  3. 2026-07-15 16:54 UTCEPSS rescore
  4. 2026-07-13 22:25 UTCEPSS rescore
  5. 2026-07-06 02:19 UTCEPSS rescore
  6. 2026-07-06 02:19 UTCEPSS rescore
  7. 2026-07-05 02:26 UTCEPSS rescore
  8. 2026-07-02 14:00 UTCEPSS rescore
  9. 2026-06-30 23:18 UTCEPSS rescore
  10. 2026-06-29 14:02 UTCEPSS rescore
  11. 2026-06-29 14:02 UTCEPSS rescore
  12. 2026-06-28 04:52 UTCEPSS rescore
  13. 2026-06-25 13:46 UTCEPSS rescore
  14. 2026-06-25 13:46 UTCEPSS rescore
  15. 2026-06-23 21:29 UTCEPSS rescore
  16. 2026-06-23 21:29 UTCEPSS rescore
  17. 2026-06-21 01:56 UTCEPSS rescore
  18. 2026-06-21 01:56 UTCEPSS rescore
  19. 2026-06-21 01:56 UTCEPSS rescore
  20. 2026-06-18 17:49 UTCEPSS rescore
  21. 2026-06-18 17:49 UTCEPSS rescore
  22. 2026-06-17 17:49 UTCEPSS rescore
  23. 2026-06-17 17:49 UTCEPSS rescore
  24. 2026-06-15 17:44 UTCEPSS rescore
  25. 2026-06-13 22:57 UTCEPSS rescore
  26. 2026-06-13 22:57 UTCEPSS rescore
  27. 2026-06-12 23:08 UTCEPSS rescore
  28. 2026-06-08 14:13 UTCEPSS rescore
  29. 2026-06-07 15:21 UTCEPSS rescore
  30. 2026-06-07 15:21 UTCEPSS rescore
  31. 2026-06-06 13:44 UTCEPSS rescore
  32. 2026-06-06 13:44 UTCEPSS rescore
  33. 2026-06-05 22:44 UTCEPSS rescore
  34. 2026-06-05 22:44 UTCEPSS rescore
  35. 2026-06-04 13:09 UTCEPSS rescore
  36. 2026-06-04 13:09 UTCEPSS rescore
  37. 2026-06-02 20:10 UTCEPSS rescore
  38. 2026-06-02 20:10 UTCEPSS rescore
  39. 2026-05-31 01:52 UTCEG score recompute
  40. 2026-05-31 01:52 UTCGHSA enrichment
  41. 2026-05-31 00:13 UTCEPSS rescore
  42. 2026-05-31 00:13 UTCEPSS rescore
  43. 2026-05-28 13:42 UTCEPSS rescore
  44. 2026-05-28 13:42 UTCEPSS rescore
  45. 2026-05-27 13:37 UTCEPSS rescore
  46. 2026-05-27 13:37 UTCEPSS rescore
  47. 2026-05-26 07:16 UTCEPSS rescore
  48. 2026-05-26 07:16 UTCEPSS rescore
  49. 2026-05-26 07:16 UTCEPSS rescore
  50. 2026-05-24 16:42 UTCEPSS rescore
  51. 2026-05-22 21:15 UTCEPSS rescore
  52. 2026-05-22 21:15 UTCEPSS rescore
  53. 2026-05-22 21:15 UTCEPSS rescore
  54. 2026-05-20 22:36 UTCEPSS rescore
  55. 2026-05-20 11:20 UTCEPSS rescore
  56. 2026-05-20 11:20 UTCEPSS rescore
  57. 2026-05-18 21:29 UTCEPSS rescore
  58. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-30281✓ verified
    First seen Jul 6, 2007

    Microsoft .Net Framework 2.0 - Multiple Null Byte Injection Vulnerabilities

    Open source ↗

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2007-0042?
CVE-2007-0042 is a high vulnerability published on July 10, 2007. 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…
When was CVE-2007-0042 disclosed?
CVE-2007-0042 was first published on July 10, 2007, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2007-0042 actively exploited?
CVE-2007-0042 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 76% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
How do I remediate CVE-2007-0042?
No fix for CVE-2007-0042 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2007-0042

Explore →

Is Your Infrastructure Affected by CVE-2007-0042?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs