What is CVE-2007-1793?A medium-severity flaw in Norton Internet Security, explained.
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.
Published 2 April 2007. Record last updated 16 June 2026. We keep this page's data up to date.
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.
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-20Improper Input Validation
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAlready on the device
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- What an attacker getsCan 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.
Timeline
- Published
- Record last updated
CVE-2007-1793 scores 43. Action: Plan remediation.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2007-1793 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2007-1793? 8 products.
The published record lists 8 products from 1 vendor. If you run one of these, check your version, then go to the fix below.
- Application
Norton Internet Security
by Symantec
Affected versions20042005200620072008 - Application
Client Security
by Symantec
Affected versions3.03.0.0.3593.0.1.10003.0.1.10013.0.1.10073.0.1.1008 - Application
Antivirus
by Symantec
Affected versions10.010.0.110.0.1.110.0.210.0.2.110.0.2.2 - Application
Norton Antivirus
by Symantec
Affected versions20042005200620072008 - Application
Norton Personal Firewall
by Symantec
Affected versions2004200520062006_9.1.0.332006_9.1.1.7 - Application
Norton System Works
by Symantec
Affected versions200420052006 - Application
Norton Antispam
by Symantec
Affected versions20042005 - Application
Norton 360
by Symantec
Affected versions1.0
How do I fix CVE-2007-1793? Four steps.
- Check whether you run itCompare 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.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack 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
17 links- Web page (opens in a new tab)securitytracker.com
- Web page (opens in a new tab)securitytracker.com
- Web page (opens in a new tab)secunia.com
- Norton Multiple Insufficient Argument Validation of Hooked SSDT Functions (opens in a new tab)matousec.com
- English (opens in a new tab)vupen.com · 2007
- Web page (opens in a new tab)osvdb.org
Does CVE-2007-1793 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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 h...
- Matched to
- Norton Internet Security on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
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.
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.
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.
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.
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.