CVE-2007-3952
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 · uneditedThe OLE2 parsing in Norman Antivirus before 5.91.02 allows remote attackers to bypass the malware detection via a crafted DOC 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 versions prior to 5.91.02 contain an integer cast vulnerability in OLE2 document parsing that allows crafted DOC files to bypass malware detection. The integer overflow in the parsing logic causes the antivirus to fail to properly analyze the malicious content, permitting infected files to pass through undetected.
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.
-
Determine installed Norman Antivirus versionLocate the Norman Antivirus application in the system (typically in Program Files) and check its version property, or use the built-in About/Help section of the application to view the version number.Affected if The displayed version is 5.90 or lower (any version <= 5.90 indicates the vulnerable version).
-
Confirm Norman Normon Antivirus product nameVerify that the installed product is specifically Norman Normon Antivirus (not another Norman product) by checking the product name in the application or installed programs list.Affected if The product is Norman Normon Antivirus and the version is 5.90 or lower.
-
Verify OLE2 document parsing is activeCheck if the antivirus has OLE2 document scanning enabled in its configuration settings, or confirm that DOC file scanning is active - the vulnerability specifically affects OLE2 document parsing functionality.Affected if OLE2/DOC document scanning is enabled and the version is 5.90 or lower, meaning the vulnerable parsing path can be triggered.
The environment is affected if Norman Normon Antivirus version 5.90 or lower is installed and OLE2 document parsing (DOC file scanning) is enabled, allowing crafted malicious DOC files to bypass detection.
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 dataUpgrade Norman Antivirus to version 5.91.02 or later to patch the integer cast vulnerability in OLE2 parsing. Ensure antivirus signature databases are current following the upgrade.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-3952 — 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-3952 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