{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2002-1777 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2002-1777 yet. Limit exposure of the affected software until one is available.","what":"CVE-2002-1777 is a high-severity vulnerability in Symantec Norton Antivirus, published on 21 Jun 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2002-1777 and fix it if it is affected.\n\nWhat it is: CVE-2002-1777 is a high-severity vulnerability in Symantec Norton Antivirus, published on 21 Jun 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2002-1777 in the wild and no public exploit code.\n\nAffected product: Symantec Norton Antivirus. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2002-1777/ (Markdown: https://insights.sbomify.com/CVE-2002-1777/index.md)","id":"CVE-2002-1777","markdown":"https://insights.sbomify.com/CVE-2002-1777/index.md","name":"CVE-2002-1777","record":{"aliases":["GHSA-3hc9-68hw-8q6p"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Symantec Norton AntiVirus","requires_auth":"none","summary":"Remote attackers can bypass email scanning in Symantec Norton AntiVirus by exploiting filename discrepancies between Content-Type and Content-Disposition headers.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"norton_antivirus","vendor":"symantec"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"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","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2002-1777","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"symantec:norton_antivirus","products":["symantec:norton_antivirus"],"type":"security_feature_bypass","year":"2002"},"n_packages":0,"n_references":4,"next":{"headline":"Security feature bypass in n/a","id":"CVE-2002-1778"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2002-1776"},"products":["n/a"],"published":"2005-06-21","related":[{"cvss_score":10,"headline":"Privilege escalation in n/a","id":"CVE-2005-2017","kev_date_added":null,"published":"2005-08-29"},{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2004-0487","kev_date_added":null,"published":"2004-06-03"},{"cvss_score":8.5,"headline":"Code injection in n/a","id":"CVE-2006-3456","kev_date_added":null,"published":"2007-05-11"},{"cvss_score":7.8,"headline":"Denial of service in n/a","id":"CVE-2002-2206","kev_date_added":null,"published":"2005-11-16"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2002-1774","kev_date_added":null,"published":"2005-06-21"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2002-1775","kev_date_added":null,"published":"2005-06-21"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2002-1776","kev_date_added":null,"published":"2005-06-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Remote attackers can bypass email scanning in Symantec Norton AntiVirus by exploiting filename discrepancies between Content-Type and Content-Disposition headers.","url":"https://insights.sbomify.com/CVE-2002-1777/"}