{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2020-5202 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2020-5202 is a medium-severity vulnerability in Debian Debian Linux, published on 21 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-5202 and fix it if it is affected.\n\nWhat it is: CVE-2020-5202 is a medium-severity vulnerability in Debian Debian Linux, published on 21 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-5202 in the wild and no public exploit code.\n\nAffected product: Debian Debian Linux. 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-2020-5202/ (Markdown: https://insights.sbomify.com/CVE-2020-5202/index.md)","id":"CVE-2020-5202","markdown":"https://insights.sbomify.com/CVE-2020-5202/index.md","name":"CVE-2020-5202","record":{"aliases":["DEBIAN-CVE-2020-5202","GHSA-ppjv-mwcc-539j","UBUNTU-CVE-2020-5202"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"apt-cacher-ng proxy","requires_auth":"low_privilege","summary":"Local attackers can hijack a hardcoded TCP port to intercept sensitive data from apt-cacher-ng administrative requests, exposing credentials or configuration details.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"apt-cacher-ng","vendor":"apt-cacher-ng_project"},{"product":"debian_linux","vendor":"debian"},{"product":"backports","vendor":"opensuse"},{"product":"leap","vendor":"opensuse"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"apt-cacher-ng through 3.3 allows local users to obtain sensitive information by hijacking the hardcoded TCP port. The /usr/lib/apt-cacher-ng/acngtool program attempts to connect to apt-cacher-ng via TCP on localhost port 3142, even if the explicit SocketPath=/var/run/apt-cacher-ng/socket command-line option is passed. The cron job /etc/cron.daily/apt-cacher-ng (which is active by default) attempts this periodically. Because 3142 is an unprivileged port, any local user can try to bind to this port and will receive requests from acngtool. There can be sensitive data in these requests, e.g., if AdminAuth is enabled in /etc/apt-cacher-ng/security.conf. This sensitive data can leak to unprivileged local users that manage to bind to this port before the apt-cacher-ng daemon can.","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":"Information disclosure in n/a","id":"CVE-2020-5202","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"debian:debian_linux","products":["debian:debian_linux","opensuse:backports","opensuse:leap"],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":6,"next":{"headline":"Fat-Free Framework arbitrary code execution","id":"CVE-2020-5203"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2020-5200"},"products":["n/a"],"published":"2020-01-21","related":[{"cvss_score":6.2,"headline":"apt-cacher-ng insecure use of /run/apt-cacher-ng","id":"CVE-2019-18899","kev_date_added":null,"published":"2020-01-23"},{"cvss_score":6.1,"headline":"Other in n/a","id":"CVE-2017-7443","kev_date_added":null,"published":"2017-04-05"},{"cvss_score":5.1,"headline":"Reflected Cross-site scripting (XSS) vulnerability in Apt-Cacher-NG","id":"CVE-2025-11146","kev_date_added":null,"published":"2025-09-29"},{"cvss_score":5.1,"headline":"Reflected Cross-site scripting (XSS) vulnerability in Apt-Cacher-NG","id":"CVE-2025-11147","kev_date_added":null,"published":"2025-09-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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Local attackers can hijack a hardcoded TCP port to intercept sensitive data from apt-cacher-ng administrative requests, exposing credentials or configuration details.","url":"https://insights.sbomify.com/CVE-2020-5202/"}