{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-20210 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2021-20210 is a high-severity denial of service vulnerability in privoxy, published on 25 Mar 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-20210 and fix it if it is affected.\n\nWhat it is: CVE-2021-20210 is a high-severity denial of service vulnerability in privoxy, published on 25 Mar 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-20210 in the wild and no public exploit code.\n\nAffected product: privoxy. 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-20210/ (Markdown: https://insights.sbomify.com/CVE-2021-20210/index.md)","id":"CVE-2021-20210","markdown":"https://insights.sbomify.com/CVE-2021-20210/index.md","name":"CVE-2021-20210","record":{"aliases":["ALPINE-CVE-2021-20210","DEBIAN-CVE-2021-20210","GHSA-j4jv-9rjv-h6jm","UBUNTU-CVE-2021-20210"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Privoxy web proxy","requires_auth":"none","summary":"A memory leak in Privoxy's status handler when no filters are configured can cause a system crash, requiring an upgrade to fix.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"privoxy","vendor":"privoxy"}],"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-401","name":"Missing Release of Memory after Effective Lifetime"}],"description":"A flaw was found in Privoxy in versions before 3.0.29. Memory leak in the show-status CGI handler when no filter files are configured can lead to a system crash.","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 privoxy","id":"CVE-2021-20210","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":"Denial of service in privoxy","id":"CVE-2021-20211"},"packages":[],"prev":{"headline":"Denial of service in privoxy","id":"CVE-2021-20209"},"products":["privoxy"],"published":"2021-03-25","related":[{"cvss_score":7.7,"headline":"Local privilege escalation from user privoxy to root","id":"CVE-2019-3699","kev_date_added":null,"published":"2020-01-24"},{"cvss_score":7.5,"headline":"Denial of service in Privoxy","id":"CVE-2021-44540","kev_date_added":null,"published":"2021-12-23"},{"cvss_score":7.5,"headline":"Denial of service in Privoxy","id":"CVE-2021-44541","kev_date_added":null,"published":"2021-12-23"},{"cvss_score":7.5,"headline":"Denial of service in Privoxy","id":"CVE-2021-44542","kev_date_added":null,"published":"2021-12-23"},{"cvss_score":7.5,"headline":"Denial of service in privoxy","id":"CVE-2021-20209","kev_date_added":null,"published":"2021-05-25"},{"cvss_score":7.5,"headline":"Denial of service in privoxy","id":"CVE-2020-35502","kev_date_added":null,"published":"2021-03-25"}],"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-03","vendors":["n/a"]},"summary":"A memory leak in Privoxy's status handler when no filters are configured can cause a system crash, requiring an upgrade to fix.","url":"https://insights.sbomify.com/CVE-2021-20210/"}