CVE-2007-3951
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMultiple buffer overflows in Norman Antivirus 5.90 allow remote attackers to execute arbitrary code via a crafted (1) ACE or (2) LZH file, resulting from an "integer cast around."
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceNorman Antivirus 5.90 contains multiple buffer overflow vulnerabilities when processing ACE and LZH archive files. The root cause is an integer cast issue that leads to incorrect buffer size calculations during archive parsing, allowing remote attackers to execute arbitrary code via specially crafted archives.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 5.90CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Norman Antivirus installationCheck for Norman Virus Control or Norman Antivirus in installed programs list via Control Panel > Programs and Features, or run 'reg query HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall' to list installed softwareAffected if Norman Virus Control or Norman Antivirus appears in the installed programs list
-
Determine installed versionOpen Norman Virus Control/Norman Antivirus and navigate to Help > About, or check the program's version property in the file system (typically in the installation directory)Affected if The reported version number is 5.90 or lower (any version <= 5.90)
-
Verify archive scanning is enabledOpen Norman Virus Control settings and check if archive scanning for ACE and LZH file types is enabled in the scanning configuration optionsAffected if Archive scanning for ACE and/or LZH files is enabled - this is the attack surface for the vulnerability
The system is affected if Norman Virus Control version 5.90 or lower is installed AND archive scanning for ACE or LZH files is enabled, as the vulnerability triggers specifically when these archive types are processed by the antivirus engine.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Norman Antivirus to a version that patches this vulnerability, or replace with an alternative antivirus solution if no patch is available. Avoid opening untrusted ACE or LZH files until the update is applied.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-3951 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-3951 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data