{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2009-0654 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2009-0654 yet. Limit exposure of the affected software until one is available.","what":"CVE-2009-0654 is a medium-severity vulnerability in Tor Tor, published on 20 Feb 2009. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2009-0654 and fix it if it is affected.\n\nWhat it is: CVE-2009-0654 is a medium-severity vulnerability in Tor Tor, published on 20 Feb 2009. 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-2009-0654 in the wild and no public exploit code.\n\nAffected product: Tor Tor. 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-2009-0654/ (Markdown: https://insights.sbomify.com/CVE-2009-0654/index.md)","id":"CVE-2009-0654","markdown":"https://insights.sbomify.com/CVE-2009-0654/index.md","name":"CVE-2009-0654","record":{"aliases":["DEBIAN-CVE-2009-0654","GHSA-39qj-vvc5-79wf"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Tor anonymity network","requires_auth":"none","summary":"Remote attackers controlling entry and exit routers can confirm communication between sender and receiver by observing cell recognition errors.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tor","vendor":"tor"}],"cvss":{"score":5.1,"severity":"medium","source":"nvd","vector":"AV:N/AC:H/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Tor 0.2.0.28, and probably 0.2.0.34 and earlier, allows remote attackers, with control of an entry router and an exit router, to confirm that a sender and receiver are communicating via vectors involving (1) replaying, (2) modifying, (3) inserting, or (4) deleting a single cell, and then observing cell recognition errors at the exit router.  NOTE: the vendor disputes the significance of this issue, noting that the product's design \"accepted end-to-end correlation as an attack that is too expensive to solve.\"","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Information disclosure in n/a","id":"CVE-2009-0654","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"tor:tor","products":["tor:tor"],"type":"information_disclosure","year":"2009"},"n_packages":0,"n_references":3,"next":{"headline":"Auth bypass in n/a","id":"CVE-2009-0655"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2009-0653"},"products":["n/a"],"published":"2009-02-20","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2010-1676","kev_date_added":null,"published":"2010-12-22"},{"cvss_score":10,"headline":"Tor before 0.2.0.34 treats incomplete IPv4 addresses as valid, which has unknown impact and attack vectors related to \"Spec conformance,\" as","id":"CVE-2009-0939","kev_date_added":null,"published":"2009-03-18"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2009-0414","kev_date_added":null,"published":"2009-02-03"},{"cvss_score":9.3,"headline":"Information disclosure in n/a","id":"CVE-2008-5398","kev_date_added":null,"published":"2008-12-09"},{"cvss_score":7.6,"headline":"Memory corruption in n/a","id":"CVE-2011-2778","kev_date_added":null,"published":"2011-12-23"},{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2006-3409","kev_date_added":null,"published":"2006-07-07"},{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2008-5397","kev_date_added":null,"published":"2008-12-09"}],"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-17","vendors":["n/a"]},"summary":"Remote attackers controlling entry and exit routers can confirm communication between sender and receiver by observing cell recognition errors.","url":"https://insights.sbomify.com/CVE-2009-0654/"}