CVE-2005-3378: n/a vulnerability

CVE-2005-3378: Multiple interpretation error in Norman 5.81 with the 5.83.02 engine allows remote attackers to bypass viru...

Multiple interpretation error in Norman 5.81 with the 5.83.02 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."

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 23:10 UTC (UTC+00:00)

Security readout for executives and security teams

This CVE describes a Norman antivirus detection bypass. Specially constructed files could be misclassified as safe because Norman interpreted an MZ magic-byte sequence as an executable indicator, while endpoint applications might still treat the same file as dangerous content. Exposure is most likely limited to legacy environments still using the named Norman version and engine, or archived mail/file scanning workflows that depended on that scanner. The source bundle does not provide CPEs or a complete affected-product list. Treat this as a legacy exposure check, not an emergency, unless Norman 5.81 or the affected engine is still protecting mail or endpoints. The business issue is misplaced trust in a scanner that may miss dangerous files. Mitigation focus: Check whether Norman 5.81 with engine 5.83.02 exists in any environment.; Review Norman or successor-vendor guidance for updates, retirement, or replacement instructions.; Do not rely on magic-byte-only file classification in mail or web filtering controls..

Prepared: Jun 29, 2026, 17:15 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2005-3378 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Oct 29, 2005, 19:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.