CVE-2002-1775: n/a vulnerability

CVE-2002-1775: NOTE: this issue has been disputed by the vendor.

NOTE: this issue has been disputed by the vendor. Symantec Norton AntiVirus (NAV) 2002 allows remote attackers to bypass the initial virus scan and cause NAV to prematurely stop scanning by using a non-RFC compliant MIME header. NOTE: the vendor has disputed this issue, acknowledging that the initial scan is bypassed, but the AutoProtect feature would detect the virus before it is executed

UnknownCVSS not scoredNot KEV-listedUpdatedAug 8, 2024, 03:34 UTC (UTC+00:00)

Security readout for executives and security teams

CVE-2002-1775 describes a disputed Norton AntiVirus 2002 email-scanning weakness. A malformed MIME header could reportedly bypass the initial scan and stop scanning early. Symantec disputed the practical impact, saying AutoProtect would still detect the virus before execution. Business urgency is mainly for legacy environments, not modern fleets. Exposure appears limited to systems still running Norton AntiVirus 2002 or relying on its email/MIME scanning path. The structured affected-product data is n/a, so asset owners should verify against local inventories rather than assume broad applicability. Low immediate priority for modern environments, but investigate if legacy antivirus remains in regulated, isolated, or archival systems. The disputed status and missing severity data make replacement and control verification more appropriate than emergency response. Mitigation focus: Check Symantec or successor vendor guidance for any historical advisory or update.; Retire or replace any remaining Norton AntiVirus 2002 installations.; Verify AutoProtect or equivalent real-time protection is enabled on legacy hosts..

Prepared: Jun 29, 2026, 19:56 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-2002-1775 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: Jun 21, 2005, 04: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

2Source 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
nav-nonrfc-bypass-protection(8390)CVE reference · vdb-entry, x_refsource_XF

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.