{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-2223 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2006-2223 is a medium-severity vulnerability in n/a, published on 5 May 2006. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2006-2223 and fix it if it is affected.\n\nWhat it is: CVE-2006-2223 is a medium-severity vulnerability in n/a, published on 5 May 2006. 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-2006-2223 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-2006-2223/ (Markdown: https://insights.sbomify.com/CVE-2006-2223/index.md)","id":"CVE-2006-2223","markdown":"https://insights.sbomify.com/CVE-2006-2223/index.md","name":"CVE-2006-2223","record":{"aliases":["GHSA-xx8x-qm77-m9x3"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Quagga routing software","requires_auth":"none","summary":"Remote attackers can obtain sensitive routing state information from Quagga RIPd when specific authentication or protocol configurations are improperly implemented.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"quagga","vendor":"quagga"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"RIPd in Quagga 0.98 and 0.99 before 20060503 does not properly implement configurations that (1) disable RIPv1 or (2) require plaintext or MD5 authentication, which allows remote attackers to obtain sensitive information (routing state) via REQUEST packets such as SEND UPDATE.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2006-05-03","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2006-05-03","kind":"exploitdb","ref":"27801","stars":null,"title":"Quagga Routing Software Suite 0.9x - RIPd RIPv1 Request Routing Table Disclosure"}],"tier":"weaponised"},"has_fix":true,"headline":"Information disclosure in n/a","id":"CVE-2006-2223","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2006"},"n_packages":0,"n_references":23,"next":{"headline":"Auth bypass in n/a","id":"CVE-2006-2224"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2006-2222"},"products":["n/a"],"published":"2006-05-05","related":[{"cvss_score":8.2,"headline":"Denial of service in Protocol","id":"CVE-2017-3224","kev_date_added":null,"published":"2018-07-24"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2021-44038","kev_date_added":null,"published":"2021-11-19"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2017-5495","kev_date_added":null,"published":"2017-01-24"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2011-3327","kev_date_added":null,"published":"2011-10-10"},{"cvss_score":6.5,"headline":"Memory corruption in n/a","id":"CVE-2010-2948","kev_date_added":null,"published":"2010-09-10"},{"cvss_score":6.3,"headline":"Denial of service in n/a","id":"CVE-2007-1995","kev_date_added":null,"published":"2007-04-12"},{"cvss_score":5,"headline":"Denial of service in n/a","id":"CVE-2012-0255","kev_date_added":null,"published":"2012-04-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":"CWE Terms of Use","name":"CWE (MITRE)"},{"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-07","vendors":["n/a"]},"summary":"Remote attackers can obtain sensitive routing state information from Quagga RIPd when specific authentication or protocol configurations are improperly implemented.","url":"https://insights.sbomify.com/CVE-2006-2223/"}