{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-2503 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2013-2503 is a medium-severity vulnerability in n/a, published on 11 Mar 2013. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-2503 and fix it if it is affected.\n\nWhat it is: CVE-2013-2503 is a medium-severity vulnerability in n/a, published on 11 Mar 2013. 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-2013-2503 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-2013-2503/ (Markdown: https://insights.sbomify.com/CVE-2013-2503/index.md)","id":"CVE-2013-2503","markdown":"https://insights.sbomify.com/CVE-2013-2503/index.md","name":"CVE-2013-2503","record":{"aliases":["DEBIAN-CVE-2013-2503","GHSA-xwv2-6j43-gjcx"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Privoxy proxy server","requires_auth":"none","summary":"Remote HTTP servers can spoof the intended proxy service by manipulating authentication headers, bypassing security controls in Privoxy.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"privoxy","vendor":"privoxy"}],"cvss":{"score":5.8,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:P/I:P/A:N","version":"2.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Privoxy before 3.0.21 does not properly handle Proxy-Authenticate and Proxy-Authorization headers in the client-server data stream, which makes it easier for remote HTTP servers to spoof the intended proxy service via a 407 (aka Proxy Authentication Required) HTTP status code.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2013-03-11","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2013-03-11","kind":"exploitdb","ref":"38377","stars":null,"title":"Privoxy Proxy - Authentication Information Disclosure"}],"tier":"weaponised"},"has_fix":true,"headline":"Security feature bypass in n/a","id":"CVE-2013-2503","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2013"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2013-2504"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2013-2501"},"products":["n/a"],"published":"2013-03-11","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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Remote HTTP servers can spoof the intended proxy service by manipulating authentication headers, bypassing security controls in Privoxy.","url":"https://insights.sbomify.com/CVE-2013-2503/"}