{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2002-1775 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2002-1775 yet. Limit exposure of the affected software until one is available.","what":"CVE-2002-1775 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, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2002-1775 and fix it if it is affected.\n\nWhat it is: CVE-2002-1775 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, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2002-1775 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-1775/ (Markdown: https://insights.sbomify.com/CVE-2002-1775/index.md)","id":"CVE-2002-1775","markdown":"https://insights.sbomify.com/CVE-2002-1775/index.md","name":"CVE-2002-1775","record":{"aliases":["GHSA-vq7q-wrc4-2qv3"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Antivirus software","requires_auth":"none","summary":"Remote attackers can bypass the initial virus scan in Symantec Norton AntiVirus 2002 using non-RFC compliant MIME headers, though AutoProtect may still detect threats.","user_interaction":"not_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 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","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-1775","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-1776"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2002-1774"},"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-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 the initial virus scan in Symantec Norton AntiVirus 2002 using non-RFC compliant MIME headers, though AutoProtect may still detect threats.","url":"https://insights.sbomify.com/CVE-2002-1775/"}