{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-34549 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2021-34549 is a high-severity denial of service vulnerability in n/a, published on 29 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-34549 and fix it if it is affected.\n\nWhat it is: CVE-2021-34549 is a high-severity denial of service vulnerability in n/a, published on 29 Jun 2021. 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-2021-34549 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-2021-34549/ (Markdown: https://insights.sbomify.com/CVE-2021-34549/index.md)","id":"CVE-2021-34549","markdown":"https://insights.sbomify.com/CVE-2021-34549/index.md","name":"CVE-2021-34549","record":{"aliases":["DEBIAN-CVE-2021-34549","GHSA-qx32-4xrf-2j53","UBUNTU-CVE-2021-34549"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Tor anonymity network","requires_auth":"none","summary":"An attacker can cause algorithm inefficiency and denial of service in Tor by triggering the use of an attacker-chosen circuit ID.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tor","vendor":"torproject"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"An issue was discovered in Tor before 0.4.6.5, aka TROVE-2021-005. Hashing is mishandled for certain retrieval of circuit data. Consequently. an attacker can trigger the use of an attacker-chosen circuit ID to cause algorithm inefficiency.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Denial of service in n/a","id":"CVE-2021-34549","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2021-34550"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2021-34548"},"products":["n/a"],"published":"2021-06-29","related":[{"cvss_score":8.9,"headline":"Race condition in Tor","id":"CVE-2026-77638","kev_date_added":null,"published":"2026-08-20"},{"cvss_score":7.5,"headline":"Memory corruption in Tor","id":"CVE-2026-77642","kev_date_added":null,"published":"2026-08-20"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2022-33903","kev_date_added":null,"published":"2022-07-17"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2021-38385","kev_date_added":null,"published":"2021-08-30"},{"cvss_score":7.5,"headline":"Security feature bypass in n/a","id":"CVE-2021-34548","kev_date_added":null,"published":"2021-06-29"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2021-34550","kev_date_added":null,"published":"2021-06-29"}],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"An attacker can cause algorithm inefficiency and denial of service in Tor by triggering the use of an attacker-chosen circuit ID.","url":"https://insights.sbomify.com/CVE-2021-34549/"}