CVE-2007-1793

MEDIUMCVSS v2 · 4.94.9—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 4.9 — v2 rates that MEDIUM (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:L/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 1.7% 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
4.9EG
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).
  • Public exploit code is available (Exploit-DB, marked verified by Exploit-DB)
CISA-KEV: Not listedEPSS PROB: 1.7%CVSS v2: 4.9Exploit: Exploit-DB (verified)Exposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

SPBBCDrv.sys in Symantec Norton Personal Firewall 2006 9.1.0.33 and 9.1.1.7 does not validate certain arguments before being passed to hooked SSDT function handlers, which allows local users to cause a denial of service (crash) or possibly execute arbitrary code via crafted arguments to the (1) NtCreateMutant and (2) NtOpenEvent functions. NOTE: it was later reported that Norton Internet Security 2008 15.0.0.60, and possibly other versions back to 2006, are also affected.

CVSS v2.0 (legacy)
4.9MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
4.9MEDIUMlow confidence
EG Risk
53
EG Risk 53/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)
Severity49% × 45%
The EG Score, 4.9 of 10.
Exploitation65% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized): a constant, not a probability.
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: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
1.7%
EPSS %ILE
76th
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.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

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

April 2, 2007

Last Modified

April 23, 2026

References (17)

15 of 17 shown · show the other 2

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 14× 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.

Showing the most recent 77 of 92 refreshes on record for this CVE.

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. 23 repeat rows among the latest 100 are merged into the row they repeat. The 15 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 13:37 UTCEPSS rescoreEPSS 1.7% · 76th percentile
  2. 2026-10-10 19:53 UTCEPSS rescoreEPSS 1.7% · 76th percentile
  3. 2026-10-09 19:59 UTCEPSS rescoreEPSS 1.7% · 76th percentile
  4. 2026-10-08 16:32 UTCEPSS rescoreEPSS 1.7% · 76th percentile
  5. 2026-10-07 23:36 UTCEPSS rescoreEPSS 1.7% · 76th percentile
  6. 2026-10-06 15:08 UTCEPSS rescoreEPSS 1.7% · 76th percentile
  7. 2026-10-05 17:37 UTCEPSS rescoreEPSS 1.7% · 76th percentile
  8. 2026-10-04 23:15 UTCEPSS rescoreEPSS 1.7% · 76th percentile
  9. 2026-09-30 14:57 UTCEPSS rescoreEPSS 1.7% · 76th percentile
  10. 2026-09-29 07:40 UTCEG score recompute
  11. 2026-09-18 19:20 UTCEPSS rescoreEPSS 1.7% · 76th percentile
  12. 2026-09-15 03:04 UTCEPSS rescoreEPSS 1.7% · 76th percentile
  13. 2026-09-13 16:40 UTCEPSS rescoreEPSS 1.7% · 76th percentile
  14. 2026-09-12 14:54 UTCEPSS rescoreEPSS 1.7% · 76th percentile
  15. 2026-09-10 09:24 UTCEPSS rescoreEPSS 1.7% · 76th percentile
  16. 2026-09-05 15:22 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  17. 2026-09-04 13:54 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  18. 2026-09-04 04:59 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  19. 2026-08-30 01:14 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  20. 2026-08-08 16:30 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  21. 2026-08-07 16:20 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  22. 2026-08-06 13:41 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  23. 2026-08-05 19:11 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  24. 2026-08-04 15:03 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  25. 2026-08-04 10:28 UTCEPSS rescoreEPSS 1.7% · 75th percentile
Show 52 more
  1. 2026-08-03 10:28 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  2. 2026-07-28 15:30 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  3. 2026-07-26 13:32 UTCEG score recompute▲ 4.90
  4. 2026-07-25 14:11 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  5. 2026-07-24 14:11 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  6. 2026-07-23 00:53 UTCEG score recompute
  7. 2026-07-23 00:32 UTCEG score recompute
  8. 2026-07-22 23:57 UTCEG score recompute
  9. 2026-07-22 21:37 UTCEG score recompute
  10. 2026-07-22 14:03 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  11. 2026-07-21 15:19 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  12. 2026-07-20 17:02 UTCEPSS rescoreEPSS 1.7% · 75th percentile
  13. 2026-07-16 16:58 UTCEPSS rescoreEPSS 1.7% · 74th percentile
  14. 2026-07-15 16:54 UTCEPSS rescoreEPSS 1.7% · 74th percentile
  15. 2026-07-15 01:55 UTCEPSS rescoreEPSS 1.7% · 74th percentile
  16. 2026-07-13 22:25 UTCEPSS rescoreEPSS 1.7% · 74th percentile
  17. 2026-07-13 06:07 UTCEPSS rescoreEPSS 1.7% · 74th percentile
  18. 2026-07-08 15:09 UTCEPSS rescoreEPSS 1.7% · 74th percentile
  19. 2026-07-06 02:19 UTCEPSS rescoreEPSS 1.7% · 74th percentile
  20. 2026-07-05 02:26 UTCEPSS rescoreEPSS 1.7% · 74th percentile
  21. 2026-07-04 06:26 UTCEPSS rescoreEPSS 1.7% · 74th percentile
  22. 2026-07-02 14:00 UTCEPSS rescoreEPSS 1.7% · 74th percentile
  23. 2026-07-01 15:02 UTCEPSS rescoreEPSS 1.7% · 74th percentile
  24. 2026-06-30 23:18 UTCEPSS rescoreEPSS 1.7% · 74th percentile
  25. 2026-06-28 14:02 UTCEPSS rescoreEPSS 1.7% · 74th percentile
  26. 2026-06-28 04:52 UTCEPSS rescoreEPSS 1.7% · 74th percentile
  27. 2026-06-25 13:46 UTCEPSS rescoreEPSS 1.7% · 74th percentile
  28. 2026-06-24 14:01 UTCEPSS rescoreEPSS 1.7% · 74th percentile
  29. 2026-06-23 21:29 UTCEPSS rescoreEPSS 1.7% · 74th percentile
  30. 2026-06-19 19:22 UTCEPSS rescoreEPSS 1.7% · 74th percentile
  31. 2026-06-18 17:49 UTCEPSS rescoreEPSS 1.7% · 74th percentile
  32. 2026-06-17 17:49 UTCEPSS rescoreEPSS 1.7% · 74th percentile
  33. 2026-06-16 17:49 UTCEPSS rescoreEPSS 1.7% · 74th percentile
  34. 2026-06-15 17:44 UTCEPSS rescoreEPSS 1.7% · 74th percentile
  35. 2026-06-14 23:13 UTCEPSS rescoreEPSS 0.3% · 51st percentile
  36. 2026-06-13 22:57 UTCEPSS rescoreEPSS 0.3% · 51st percentile
  37. 2026-06-12 23:08 UTCEPSS rescoreEPSS 0.3% · 51st percentile
  38. 2026-06-08 14:13 UTCEPSS rescoreEPSS 0.3% · 51st percentile
  39. 2026-06-07 15:21 UTCEPSS rescoreEPSS 0.3% · 51st percentile
  40. 2026-06-06 13:44 UTCEPSS rescoreEPSS 0.3% · 51st percentile
  41. 2026-06-05 22:44 UTCEPSS rescoreEPSS 0.3% · 51st percentile
  42. 2026-06-05 06:07 UTCEPSS rescoreEPSS 0.3% · 51st percentile
  43. 2026-06-04 13:09 UTCEPSS rescoreEPSS 0.3% · 51st percentile
  44. 2026-06-02 20:10 UTCEPSS rescoreEPSS 0.3% · 51st percentile
  45. 2026-06-01 13:49 UTCEPSS rescoreEPSS 0.3% · 51st percentile
  46. 2026-05-31 22:28 UTCEPSS rescoreEPSS 0.3% · 51st percentile
  47. 2026-05-31 03:29 UTCEG score recompute
  48. 2026-05-31 03:29 UTCGHSA enrichmentGHSA-6jrx-j7r6-m2m9
  49. 2026-05-31 00:13 UTCEPSS rescoreEPSS 0.3% · 51st percentile
  50. 2026-05-29 13:40 UTCEPSS rescoreEPSS 0.3% · 51st percentile
  51. 2026-05-28 13:42 UTCEPSS rescoreEPSS 0.3% · 51st percentile
  52. 2026-05-27 13:37 UTCEPSS rescoreEPSS 0.3% · 51st percentile

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Exploit-DB entry). No release with the fix is confirmed, so defenders should restrict or isolate affected systems accordingly until one is applied.

  • Exploit-DBEDB-29810✓ verified
    Published Apr 1, 2007

    Symantec (Multiple Products) - 'SPBBCDrv' Driver Local Denial of Service

    Open source ↗

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2007-1793?
CVE-2007-1793 is a medium-severity vulnerability; its CVE record was published on April 2, 2007. SPBBCDrv.sys in Symantec Norton Personal Firewall 2006 9.1.0.33 and 9.1.1.7 does not validate certain arguments before being passed to hooked SSDT function handlers, which allows local users to cause a denial of service (crash) or possibly execute arbitrary code via crafted arguments to the (1)…
When was CVE-2007-1793 made public?
CVE-2007-1793 was made public on April 1, 2007: 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 April 2, 2007. EchelonGraph's copy of the record carries a last-modified date of April 23, 2026; the record at its source may have been updated since.
Is CVE-2007-1793 actively exploited?
CVE-2007-1793 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: Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 1.7% probability of exploitation in the next 30 days (76th percentile of EPSS-scored CVEs).
How do I remediate CVE-2007-1793?
A fix for CVE-2007-1793 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2007-1793?

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

Book a Demo →Browse All CVEs