dbcve.org
Antivirus Scan EngineApplication · Symantec

CVE-2007-0447

HIGH · 9.3 CVSS v2.0 Published 2007-10-05
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
Heap-based buffer overflow in the Decomposer component in multiple Symantec products allows remote attackers to execute arbitrary code via multiple crafted CAB archives.

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
How this class of weakness works · CWE-119

The program reads or writes outside the bounds of an allocated buffer, corrupting adjacent memory. With crafted input an attacker can overwrite control data and, with effort, redirect execution to their own code. Remediation ranges from bounds checking and safe library functions to compiler mitigations, usually alongside a careful audit of the surrounding code.

General guidance for the memory buffer bounds error class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Antivirus Scan EngineApplication
Affected:= 4.0= 4.1= 4.1.8= 4.3= 4.3.3= 4.3.7.27= 4.3.8.29= 4.3.12= 5.0= 5.0.1
Brightmail AntispamApplication
Affected:= 4.0= 5.5= 6.0= 6.0.1= 6.0.2= 6.0.3= 6.0.4
Client SecurityApplication
Affected:= 2.0= 2.0.1_build_9.0.1.1000= 2.0.2_build_9.0.2.1000= 2.0.3_build_9.0.3.1000= 2.0.4= 2.0.5_build_1100_mp1= 2.0.6= 3.0= 3.0.0.359= 3.0.1.1000= 3.0.1.1001= 3.0.1.1007
Mail SecurityApplication
Affected:= 4.0= 4.0.1= 4.1= 4.5= 4.5.4.743= 4.5_build_719= 4.5_build_736= 4.5_build_741= 4.6.1.107= 4.6.3= 4.6_build_97= 5.0
Norton AntivirusApplication
Affected:all versions= 9.0= 9.0.0= 9.0.0.338= 9.0.1= 9.0.1.1.1000= 9.0.2= 9.0.2.1000= 9.0.3= 9.0.3.1000= 9.0.4= 9.0.5
Norton Internet SecurityApplication
Affected:= 3.0= 2004= 2005= 2006
Norton Personal FirewallApplication
Affected:= 2006= 2006_9.1.0.33= 2006_9.1.1.7
Norton System WorksApplication
Affected:= 3.0= 2004= 2005= 2006

CVSS 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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch securityresponse.symantec.com →
Recommended fix Moderate confidence

Move to a currently supported Symantec/Norton product (Norton 360 or Norton Security) - the affected products are all end-of-life and no longer receive updates

  1. 1. Identify the specific Symantec product and version currently installed from the affected list.
  2. 2. Visit the vendor security response page at http://securityresponse.symantec.com/avcenter/security/Content/2007.07.11f.html to obtain the specific patch or fixed version for your product.
  3. 3. If a vendor patch is available, apply it according to Symantec's instructions.
  4. 4. If no patch is available or the product is end-of-life, migrate to a currently supported Symantec security product (e.g., Norton 360, Norton Security Premium).
  5. 5. As a temporary mitigation, disable automatic scanning of CAB archives or restrict handling of untrusted CAB files until the patch can be applied.
  6. 6. Verify the fix by checking the product version or applying the vendor patch.
Caveat These are very old (2004-2007) products that have reached end-of-life; upgrading to modern Norton products may require new licenses and may change user interface/workflow

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $3,200. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-0447 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-0447 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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