CVE-2006-3942

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:N/I:N/A:C. 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 75.0% 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 verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 75%
  • Public exploit code is available (Metasploit, Exploit-DB, marked verified by Exploit-DB)
CISA-KEV: Not listedEPSS PROB: 75%CVSS v2: 7.8Exploit: Metasploit · Exploit-DB (verified)Exposed services: Not assessed

No fix has been recorded since the CVE record was published in 2006 — isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

The server driver (srv.sys) in Microsoft Windows NT 4.0, 2000, XP, and Server 2003 allows remote attackers to cause a denial of service (system crash) via an SMB_COM_TRANSACTION SMB message that contains a string without null character termination, which leads to a NULL dereference in the ExecuteTransaction function, possibly related to an "SMB PIPE," aka the "Mailslot DOS" vulnerability. NOTE: the name "Mailslot DOS" was derived from incomplete initial research; the vulnerability is not associated with a mailslot.

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/100

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 (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation75% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability30% × 15%
EchelonGraph's default before algorithm v3.4: CISA had not published Automatable for this CVE.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track or Track* at medium and Track* or Attend at high mission impact.
Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix has been recorded since the CVE record was published in 2006. Isolate the affected system within your standard update timelines at low or medium mission impact and sooner than that at high (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.
EPSS PROB
75%
EPSS %ILE
99th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track or Track* at medium and Track* or Attend at high mission impact.

No fix has been recorded since the CVE record was published in 2006. Isolate the affected system within your standard update timelines at low or medium mission impact and sooner than that at high (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

Published

July 31, 2006

Last Modified

April 16, 2026

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 15 repeat rows among the latest 70 are merged into the row they repeat.

  1. 2026-10-10 19:53 UTCEPSS rescoreEPSS 75% · 99th percentile
  2. 2026-10-08 16:32 UTCEPSS rescoreEPSS 75% · 99th percentile
  3. 2026-10-07 23:36 UTCEPSS rescoreEPSS 75% · 99th percentile
  4. 2026-09-29 03:01 UTCEG score recompute
  5. 2026-09-18 19:20 UTCEPSS rescoreEPSS 75% · 99th percentile
  6. 2026-09-17 19:20 UTCEPSS rescoreEPSS 75% · 99th percentile
  7. 2026-09-13 16:39 UTCEPSS rescoreEPSS 75% · 99th percentile
  8. 2026-09-12 14:54 UTCEPSS rescoreEPSS 75% · 99th percentile
  9. 2026-09-10 09:23 UTCEPSS rescoreEPSS 75% · 99th percentile
  10. 2026-09-05 15:21 UTCEPSS rescoreEPSS 75% · 99th percentile
  11. 2026-08-30 01:14 UTCEPSS rescoreEPSS 75% · 99th percentile
  12. 2026-08-08 16:30 UTCEPSS rescoreEPSS 75% · 99th percentile
  13. 2026-08-05 19:11 UTCEPSS rescoreEPSS 75% · 99th percentile
  14. 2026-07-26 13:29 UTCEG score recompute▲ 7.80
  15. 2026-07-24 14:11 UTCEPSS rescoreEPSS 75% · 99th percentile
  16. 2026-07-23 00:51 UTCEG score recompute
  17. 2026-07-23 00:30 UTCEG score recompute▼ 7.40
  18. 2026-07-22 23:55 UTCEG score recompute▲ 7.40
  19. 2026-07-22 21:35 UTCEG score recompute▼ 9.00
  20. 2026-07-20 17:02 UTCEPSS rescoreEPSS 75% · 99th percentile
  21. 2026-07-18 09:59 UTCEPSS rescoreEPSS 76% · 99th percentile
  22. 2026-07-16 16:58 UTCEPSS rescoreEPSS 76% · 99th percentile
  23. 2026-07-15 16:53 UTCEPSS rescoreEPSS 76% · 99th percentile
  24. 2026-07-15 01:55 UTCEPSS rescoreEPSS 76% · 99th percentile
  25. 2026-07-13 06:07 UTCEPSS rescoreEPSS 76% · 99th percentile
Show 30 more
  1. 2026-07-11 08:22 UTCEPSS rescoreEPSS 76% · 99th percentile
  2. 2026-07-09 19:03 UTCEPSS rescoreEPSS 76% · 99th percentile
  3. 2026-07-04 06:26 UTCEPSS rescoreEPSS 76% · 99th percentile
  4. 2026-07-01 15:01 UTCEPSS rescoreEPSS 76% · 99th percentile
  5. 2026-06-27 03:04 UTCEPSS rescoreEPSS 74% · 99th percentile
  6. 2026-06-25 13:46 UTCEPSS rescoreEPSS 74% · 99th percentile
  7. 2026-06-24 14:01 UTCEPSS rescoreEPSS 74% · 99th percentile
  8. 2026-06-23 21:29 UTCEPSS rescoreEPSS 74% · 99th percentile
  9. 2026-06-18 17:49 UTCEPSS rescoreEPSS 74% · 99th percentile
  10. 2026-06-17 17:49 UTCEPSS rescoreEPSS 74% · 99th percentile
  11. 2026-06-15 17:44 UTCEPSS rescoreEPSS 74% · 99th percentile
  12. 2026-06-13 22:56 UTCEPSS rescoreEPSS 86% · 99th percentile
  13. 2026-06-12 23:08 UTCEPSS rescoreEPSS 86% · 99th percentile
  14. 2026-06-10 22:14 UTCEPSS rescoreEPSS 86% · 99th percentile
  15. 2026-06-10 13:17 UTCEPSS rescoreEPSS 86% · 99th percentile
  16. 2026-06-07 15:21 UTCEPSS rescoreEPSS 86% · 99th percentile
  17. 2026-06-05 22:43 UTCEPSS rescoreEPSS 86% · 99th percentile
  18. 2026-06-04 13:09 UTCEPSS rescoreEPSS 86% · 99th percentile
  19. 2026-06-01 13:49 UTCEPSS rescoreEPSS 86% · 99th percentile
  20. 2026-05-31 07:26 UTCEG score recompute
  21. 2026-05-31 07:26 UTCGHSA enrichmentGHSA-3f78-rrw8-v6hw · GitHub severity HIGH
  22. 2026-05-31 00:13 UTCEPSS rescoreEPSS 86% · 99th percentile
  23. 2026-05-29 13:40 UTCEPSS rescoreEPSS 86% · 99th percentile
  24. 2026-05-28 13:42 UTCEPSS rescoreEPSS 86% · 99th percentile
  25. 2026-05-27 13:37 UTCEPSS rescoreEPSS 86% · 99th percentile
  26. 2026-05-26 07:16 UTCEPSS rescoreEPSS 86% · 99th percentile
  27. 2026-05-24 16:42 UTCEPSS rescoreEPSS 86% · 99th percentile
  28. 2026-05-22 21:15 UTCEPSS rescoreEPSS 86% · 99th percentile
  29. 2026-05-20 22:36 UTCEPSS rescoreEPSS 86% · 99th percentile
  30. 2026-05-18 21:29 UTCEPSS rescoreEPSS 86% · 99th percentile

Publicly available exploits

(3 references)

Public exploit code is referenced for this CVE (2 Metasploit modules, 1 Exploit-DB entry). No fix is on record, so defenders should restrict or isolate affected systems accordingly.

  • Metasploitauxiliary/dos/windows/smb/ms06_063_trans✓ verified
    Published Oct 10, 2006

    Microsoft SRV.SYS Pipe Transaction No Null

    Open source ↗
  • Metasploitauxiliary/dos/windows/smb/ms06_035_mailslot✓ verified
    Published Aug 15, 2006

    Microsoft SRV.SYS Mailslot Write Corruption

    Open source ↗
  • Exploit-DBEDB-2057✓ verified
    Published Jul 21, 2006

    Microsoft Windows - Mailslot Ring0 Memory Corruption (MS06-035)

    Open source ↗

Frequently asked(4)

What is CVE-2006-3942?
CVE-2006-3942 is a high-severity vulnerability; its CVE record was published on July 31, 2006. The server driver (srv.sys) in Microsoft Windows NT 4.0, 2000, XP, and Server 2003 allows remote attackers to cause a denial of service (system crash) via an SMBCOMTRANSACTION SMB message that contains a string without null character termination, which leads to a NULL dereference in the…
When was CVE-2006-3942 made public?
CVE-2006-3942 was made public on July 28, 2006: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on July 31, 2006. EchelonGraph's copy of the record carries a last-modified date of April 16, 2026; the record at its source may have been updated since.
Is CVE-2006-3942 actively exploited?
CVE-2006-3942 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it, and Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 75% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
How do I remediate CVE-2006-3942?
No fix for CVE-2006-3942 has been recorded since its CVE record was published in 2006, and EchelonGraph holds no vendor advisory for it. Isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2006-3942

Explore →

Is Your Infrastructure Affected by CVE-2006-3942?

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