CVE-2002-1777: n/a vulnerability

CVE-2002-1777: 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 e-mail scanning via a filename in the Content-Type field with an excluded extension such as .nch or .dbx, but a malicious extension in the Content-Disposition field, which is used by Outlook to obtain the file name. NOTE: the vendor has disputed this issue, acknowledging that the initial scan is bypassed, but Norton AntiVirus or the Office plug-in 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

This is a disputed, legacy email-scanning bypass report for Symantec Norton AntiVirus 2002. The claim is that a crafted attachment name could avoid initial email scanning. Symantec disputed the security impact, saying Norton or the Office plug-in would still detect the virus before execution. Exposure appears limited to historical environments using Norton AntiVirus 2002 with Outlook-style email attachment handling. The source bundle does not provide CPEs, supported affected versions, or current product impact, so modern exposure cannot be confirmed from these sources. Low immediate urgency unless the organization still runs unsupported early-2000s antivirus or mail clients. The main business issue is legacy control assurance, not a confirmed active threat. Mitigation focus: Check Symantec guidance for historical advisories or replacement recommendations.; Identify and retire any remaining Norton AntiVirus 2002 deployments.; Use supported endpoint protection and email security controls..

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-1777 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-contenttype-bypass-protection(8392)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.