# What is CVE-2007-1793?

> CVE-2007-1793 is a medium-severity flaw (CVSS 4.9) in Norton Internet Security from Symantec, published on 2 April 2007. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 1.7%. If you run an affected version, plan in the vendor’s fix.

Canonical page: https://www.precursorintelligence.com/what-is/cve-2007-1793

## At a glance

- **Verdict:** Plan it in. No sign of exploitation and a low forecast. Patch it in your normal update cycle.
- **Precursor Intelligence risk score:** 43 out of 100 (Medium); action: Plan remediation. Kept up to date as the evidence changes.
- **Severity:** Medium (CVSS 4.9 out of 10)
- **Known to be exploited:** No, not on the list of flaws known to be exploited today
- **Chance of use in the next 30 days:** 1.7% (latest exploit-likelihood forecast)
- **Published:** 2 April 2007
- **Record last updated:** 16 June 2026
- **Main product:** Norton Internet Security from Symantec
- **Affected products:** 8

## What is CVE-2007-1793? In plain terms

An attacker has to be already on the device without logging in. If it works, the attacker can take it offline.

### The official description

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.

### What kind of flaw is it?

- CWE-20: Improper Input Validation

### How an attack on it works

- Where an attacker can be: Already on the device
- How hard it is to pull off: Easy: no special conditions
- Login needed first: No login needed
- What an attacker gets: Can take it offline

Severity vector: `AV:L/AC:L/Au:N/C:N/I:N/A:C`

## Is CVE-2007-1793 being exploited? Not that we know of

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 1.7%. That can change at any time, which is why we keep watching.

Exploit likelihood over the last 7 days: 1.7%, 1.7%, 1.7%, 1.7%, 1.7%, 1.7%, 1.7%.

### Timeline

- 2 April 2007: Published
- 16 June 2026: Record last updated

### How Precursor Intelligence ranks it

CVE-2007-1793 scores **43 out of 100 (Medium)**, with the action "Plan remediation".

Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less:

- Evidence it is being exploited: biggest factor
- How severe it is: strong factor
- How widely exposed it is: smaller factor
- Threat activity around it: smaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it.

## Who is affected by CVE-2007-1793?

The published record lists 8 products.

- [Norton Internet Security](https://www.precursorintelligence.com/product/symantec/norton_internet_security) by [Symantec](https://www.precursorintelligence.com/vendors/symantec) (Application): 2004, 2005, 2006, 2007, 2008
- [Client Security](https://www.precursorintelligence.com/product/symantec/client_security) by [Symantec](https://www.precursorintelligence.com/vendors/symantec) (Application): 3.0, 3.0.0.359, 3.0.1.1000, 3.0.1.1001, 3.0.1.1007, 3.0.1.1008, 3.0.1.1009, 3.0.2, 3.0.2.2000, 3.0.2.2001, 3.0.2.2002, 3.0.2.2010, 3.0.2.2011, 3.0.2.2020, 3.0.2.2021, 3.1, 3.1.0.396, 3.1.0.401, 3.1.394, 3.1.396, 3.1.400, 3.1.401
- [Antivirus](https://www.precursorintelligence.com/product/symantec/antivirus) by [Symantec](https://www.precursorintelligence.com/vendors/symantec) (Application): 10.0, 10.0.1, 10.0.1.1, 10.0.2, 10.0.2.1, 10.0.2.2, 10.0.3, 10.0.4, 10.0.5, 10.0.6, 10.0.7, 10.0.8, 10.0.9
- [Norton Antivirus](https://www.precursorintelligence.com/product/symantec/norton_antivirus) by [Symantec](https://www.precursorintelligence.com/vendors/symantec) (Application): 2004, 2005, 2006, 2007, 2008
- [Norton Personal Firewall](https://www.precursorintelligence.com/product/symantec/norton_personal_firewall) by [Symantec](https://www.precursorintelligence.com/vendors/symantec) (Application): 2004, 2005, 2006, 2006_9.1.0.33, 2006_9.1.1.7
- [Norton System Works](https://www.precursorintelligence.com/product/symantec/norton_system_works) by [Symantec](https://www.precursorintelligence.com/vendors/symantec) (Application): 2004, 2005, 2006
- [Norton Antispam](https://www.precursorintelligence.com/product/symantec/norton_antispam) by [Symantec](https://www.precursorintelligence.com/vendors/symantec) (Application): 2004, 2005
- [Norton 360](https://www.precursorintelligence.com/product/symantec/norton_360) by [Symantec](https://www.precursorintelligence.com/vendors/symantec) (Application): 1.0

## How do I fix CVE-2007-1793?

1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

### References

- [securitytracker.com](http://www.securitytracker.com/id?1017837) (Patch)
- [securitytracker.com](http://www.securitytracker.com/id?1017838) (Patch)
- [secunia.com](http://secunia.com/advisories/24677) (Vendor advisory)
- [matousec.com](http://www.matousec.com/info/advisories/Norton-Multiple-insufficient-argument-validation-of-hooked-SSDT-functions.php) (Vendor advisory)
- [vupen.com](http://www.vupen.com/english/advisories/2007/1192) (Vendor advisory)
- [osvdb.org](http://osvdb.org/34692)
- [securityresponse.symantec.com](http://securityresponse.symantec.com/avcenter/security/Content/2008.12.12.html)
- [matousec.com](http://www.matousec.com/info/advisories/plague-in-security-software-drivers.php)
- [matousec.com](http://www.matousec.com/projects/windows-personal-firewall-analysis/plague-in-security-software-drivers.php)
- [securityfocus.com](http://www.securityfocus.com/archive/1/464456/100/0/threaded)
- [securityfocus.com](http://www.securityfocus.com/archive/1/479830/100/0/threaded)
- [securityfocus.com](http://www.securityfocus.com/bid/23241) (Exploit)
- [securitytracker.com](http://www.securitytracker.com/id?1021386)
- [securitytracker.com](http://www.securitytracker.com/id?1021387)
- [securitytracker.com](http://www.securitytracker.com/id?1021388)
- [securitytracker.com](http://www.securitytracker.com/id?1021389)
- [exchange.xforce.ibmcloud.com](https://exchange.xforce.ibmcloud.com/vulnerabilities/33352)

## Questions

### What is CVE-2007-1793?

CVE-2007-1793 is a medium-severity flaw in Norton Internet Security from Symantec, published on 2 April 2007. An attacker has to be already on the device without logging in. If it works, the attacker can take it offline.

### How serious is CVE-2007-1793?

It scores 4.9 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2007-1793 is 43 out of 100, which is Medium. Its action is "Plan remediation". No sign of exploitation and a low forecast. Patch it in your normal update cycle.

### Is CVE-2007-1793 being exploited?

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 1.7%. That can change at any time, which is why we keep watching.

### Which versions does CVE-2007-1793 affect?

For Norton Internet Security from Symantec: 2004, 2005, 2006, 2007, 2008. The record lists 8 products in all, each with its versions, under "Who is affected" on this page.

### How do I fix CVE-2007-1793?

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

## Does CVE-2007-1793 affect you?

Precursor Intelligence keeps checking for you:

- **Tell us what you run.** Pick your software from a list, or let us work it out from your website.
- **We match it to every flaw.** Over 400,000 published flaws, checked against your list.
- **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it.
- **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools.

Start free (no card, nothing to install): https://www.precursorintelligence.com/register
Book a demo: https://www.precursorintelligence.com/contact