{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-14971 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-14971 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-14971 is a high-severity code injection vulnerability in n/a, published on 23 Jun 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-14971 and fix it if it is affected.\n\nWhat it is: CVE-2020-14971 is a high-severity code injection vulnerability in n/a, published on 23 Jun 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-14971 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-2020-14971/ (Markdown: https://insights.sbomify.com/CVE-2020-14971/index.md)","id":"CVE-2020-14971","markdown":"https://insights.sbomify.com/CVE-2020-14971/index.md","name":"CVE-2020-14971","record":{"aliases":["GHSA-wjqw-p6cv-p8gj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Pi-hole DNS server","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary code by modifying Teleporter backup files and restoring them via the web interface.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pi-hole","vendor":"pi-hole"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Pi-hole through 5.0 allows code injection in piholedhcp (the Static DHCP Leases section) by modifying Teleporter backup files and then restoring them. This occurs in settings.php. To exploit this, an attacker would request a backup of limited files via teleporter.php. These are placed into a .tar.gz archive. The attacker then modifies the host parameter in dnsmasq.d files, and then compresses and uploads these files again.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Code injection in n/a","id":"CVE-2020-14971","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2020"},"n_packages":0,"n_references":4,"next":{"headline":"SQL injection in n/a","id":"CVE-2020-14972"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2020-14969"},"products":["n/a"],"published":"2020-06-23","related":[{"cvss_score":9.1,"headline":"Pi-Hole AdminLTE Remote Code Execution","id":"CVE-2020-8816","kev_date_added":"2021-12-10","published":"2020-05-29"},{"cvss_score":9,"headline":"Pi-Hole AdminLTE Whitelist (now 'Web Allowlist') Remote Command Execution","id":"CVE-2025-34087","kev_date_added":null,"published":"2025-07-03"},{"cvss_score":8.8,"headline":"Pi-hole: Local privilege escalation from `pihole` user to root via `/etc/pihole/logrotate`","id":"CVE-2026-50130","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2020-11108","kev_date_added":null,"published":"2020-05-11"},{"cvss_score":8.8,"headline":"Pi-Hole 4.3 allows Command Injection.","id":"CVE-2019-13051","kev_date_added":null,"published":"2019-10-09"},{"cvss_score":8.6,"headline":"Pi-hole Blind Server-Side Request Forgery (SSRF) vulnerability can lead to Remote Code Execution (RCE)","id":"CVE-2024-34361","kev_date_added":null,"published":"2024-07-05"},{"cvss_score":7.8,"headline":"Command injection in n/a","id":"CVE-2020-12620","kev_date_added":null,"published":"2020-07-30"}],"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":"Attackers can execute arbitrary code by modifying Teleporter backup files and restoring them via the web interface.","url":"https://insights.sbomify.com/CVE-2020-14971/"}