{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2002-1967 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2002-1967 yet. Limit exposure of the affected software until one is available.","what":"CVE-2002-1967 is a medium-severity denial of service vulnerability in n/a, published on 28 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-1967 and fix it if it is affected.\n\nWhat it is: CVE-2002-1967 is a medium-severity denial of service vulnerability in n/a, published on 28 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-1967 in the wild and no public exploit code.\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-2002-1967/ (Markdown: https://insights.sbomify.com/CVE-2002-1967/index.md)","id":"CVE-2002-1967","markdown":"https://insights.sbomify.com/CVE-2002-1967/index.md","name":"CVE-2002-1967","record":{"aliases":["GHSA-4q65-h4xr-qhqj"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"IRC client","requires_auth":"none","summary":"Remote attackers can cause a denial of service in XiRCON IRC client by sending long CTCP, primsg, msg, or notice commands.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"xircon","vendor":"mark_hanson"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:N/A:P","version":"2.0"},"cwes":[],"description":"Buffer overflow in XiRCON 1.0 Beta 4 allows remote attackers to cause a denial of service (disconnect) via a long (1) ctcp, (2) primsg, (3) msg, or (4) notice command.","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":"Denial of service in n/a","id":"CVE-2002-1967","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2002"},"n_packages":0,"n_references":3,"next":{"headline":"Misconfiguration in n/a","id":"CVE-2002-1968"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2002-1966"},"products":["n/a"],"published":"2005-06-28","related":[],"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-09-16","vendors":["n/a"]},"summary":"Remote attackers can cause a denial of service in XiRCON IRC client by sending long CTCP, primsg, msg, or notice commands.","url":"https://insights.sbomify.com/CVE-2002-1967/"}