{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-1983 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2016-1983 is a high-severity denial of service vulnerability in n/a, published on 27 Jan 2016. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-1983 and fix it if it is affected.\n\nWhat it is: CVE-2016-1983 is a high-severity denial of service vulnerability in n/a, published on 27 Jan 2016. 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-2016-1983 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-2016-1983/ (Markdown: https://insights.sbomify.com/CVE-2016-1983/index.md)","id":"CVE-2016-1983","markdown":"https://insights.sbomify.com/CVE-2016-1983/index.md","name":"CVE-2016-1983","record":{"aliases":["DEBIAN-CVE-2016-1983","GHSA-6frp-gfc5-q2xj"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Privoxy proxy server","requires_auth":"none","summary":"Remote attackers can crash the Privoxy proxy server by sending an empty HTTP Host header, causing a denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"privoxy","vendor":"privoxy"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"The client_host function in parsers.c in Privoxy before 3.0.24 allows remote attackers to cause a denial of service (invalid read and crash) via an empty HTTP Host header.","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-2016-1983","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2016"},"n_packages":0,"n_references":7,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2016-1984"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2016-1982"},"products":["n/a"],"published":"2016-01-27","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"},{"cvss_score":7.5,"headline":"Denial of service in privoxy","id":"CVE-2021-20210","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-05","vendors":["n/a"]},"summary":"Remote attackers can crash the Privoxy proxy server by sending an empty HTTP Host header, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2016-1983/"}