CVE-2005-3379
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 interpretation error in Trend Micro (1) PC-Cillin 2005 12.0.1244 with the 7.510.1002 engine and (2) OfficeScan 7.0 with the 7.510.1002 engine allows remote attackers to bypass virus scanning via a file such as BAT, HTML, and EML with an "MZ" magic byte sequence which is normally associated with EXE, which causes the file to be treated as a safe type that could still be executed as a dangerous file type by applications on the end system, as demonstrated by a "triple headed" program that contains EXE, EML, and HTML content, aka the "magic byte bug."
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 confidenceTrend Micro PC-Cillin 2005 and OfficeScan 7.0 antivirus engines misidentify files containing 'MZ' magic bytes (normally EXE signatures) embedded in BAT, HTML, or EML files, causing the scanner to treat them as safe when they could still be executed as dangerous code on end systems.
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= 7.0_engine_7.510.1002= 12.0.1244_engine_7.510.1002CVSS 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
- High
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:H/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.
-
Identify the installed Trend Micro productCheck the installed Trend Micro endpoint protection product name and version. On Windows, look in Add/Remove Programs or check the program directory for OfficeScan or PC-Cillin.Affected if Product is Trend Micro OfficeScan 7.0 or Trend Micro PC-Cillin 2005
-
Verify the antivirus engine versionCheck the engine version in the Trend Micro product interface or configuration. Look for engine version 7.510.1002 specifically.Affected if Engine version equals 7.510.1002
-
Confirm file type scanning is enabled for BAT filesIn the antivirus console, verify if scanning of .BAT (batch) files is enabled in the real-time or on-demand scan configuration.Affected if BAT file scanning is enabled and the engine version is 7.510.1002
-
Confirm file type scanning is enabled for HTML filesIn the antivirus console, verify if scanning of .HTML files is enabled in the real-time or on-demand scan configuration.Affected if HTML file scanning is enabled and the engine version is 7.510.1002
-
Confirm file type scanning is enabled for EML filesIn the antivirus console, verify if scanning of .EML (email message) files is enabled in the real-time or on-demand scan configuration.Affected if EML file scanning is enabled and the engine version is 7.510.1002
You are affected if you have OfficeScan 7.0 or PC-Cillin 2005 with engine version 7.510.1002 and have BAT, HTML, or EML file scanning enabled, as the scanner will fail to detect malicious code embedded in these files.
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 to patched versions of Trend Micro endpoint protection products; legacy versions PC-Cillin 2005 and OfficeScan 7.0 are end-of-life and should be replaced with current supported versions.
- 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-2005-3379 — 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-2005-3379 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