{"answers":{"affected":"It affects 5 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-0445 exists.","fix":"No fix has been published for CVE-2004-0445 yet. Limit exposure of the affected software until one is available.","what":"CVE-2004-0445 is a low-severity denial of service vulnerability in n/a, published on 20 May 2004. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2004-0445 and fix it if it is affected.\n\nWhat it is: CVE-2004-0445 is a low-severity denial of service vulnerability in n/a, published on 20 May 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-0445 exists.\n\nAffected product: n/a. 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-2004-0445/ (Markdown: https://insights.sbomify.com/CVE-2004-0445/index.md)","id":"CVE-2004-0445","markdown":"https://insights.sbomify.com/CVE-2004-0445/index.md","name":"CVE-2004-0445","record":{"aliases":["GHSA-6p52-7j69-f67w"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Symantec Norton Security","requires_auth":"none","summary":"Remote attackers can cause a denial of service via infinite loop in the SYMDNS.SYS driver by sending a malicious DNS response.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"client_firewall","vendor":"symantec"},{"product":"client_security","vendor":"symantec"},{"product":"norton_antispam","vendor":"symantec"},{"product":"norton_internet_security","vendor":"symantec"},{"product":"norton_personal_firewall","vendor":"symantec"}],"cvss":{"score":2.6,"severity":"low","source":"nvd","vector":"AV:N/AC:H/Au:N/C:N/I:N/A:P","version":"2.0"},"cwes":[],"description":"The SYMDNS.SYS driver in Symantec Norton Internet Security and Professional 2002 through 2004, Norton Personal Firewall 2002 through 2004, Norton AntiSpam 2004, Client Firewall 5.01 and 5.1.1, and Client Security 1.0 through 2.0 allows remote attackers to cause a denial of service (CPU consumption from infinite loop) via a DNS response with a compressed name pointer that points to itself.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2004-05-16","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2004-05-16","kind":"exploitdb","ref":"299","stars":null,"title":"Symantec Multiple Firewall - DNS Response Denial of Service"}],"tier":"weaponised"},"has_fix":null,"headline":"Denial of service in n/a","id":"CVE-2004-0445","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2004"},"n_packages":0,"n_references":11,"next":{"headline":"Unknown vulnerability in Linux before 2.4.26 for IA64 allows local users to cause a denial of service, with unknown impact.","id":"CVE-2004-0447"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2004-0444"},"products":["n/a"],"published":"2004-05-20","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2004-0444","kev_date_added":null,"published":"2004-05-20"},{"cvss_score":5,"headline":"Denial of service in n/a","id":"CVE-2004-0375","kev_date_added":null,"published":"2004-05-05"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Remote attackers can cause a denial of service via infinite loop in the SYMDNS.SYS driver by sending a malicious DNS response.","url":"https://insights.sbomify.com/CVE-2004-0445/"}