{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-2043 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-2043 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-2043 is a low-severity vulnerability in Paloaltonetworks Pan-Os, published on 9 Sep 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-2043 and fix it if it is affected.\n\nWhat it is: CVE-2020-2043 is a low-severity vulnerability in Paloaltonetworks Pan-Os, published on 9 Sep 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-2043 in the wild and no public exploit code.\n\nAffected product: Paloaltonetworks Pan-Os. 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-2043/ (Markdown: https://insights.sbomify.com/CVE-2020-2043/index.md)","id":"CVE-2020-2043","markdown":"https://insights.sbomify.com/CVE-2020-2043/index.md","name":"CVE-2020-2043","record":{"aliases":["GHSA-8743-86pf-fx3j"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"PAN-OS firewall","requires_auth":"low_privilege","summary":"Attackers with log access can read clear-text passwords if the after-change-detail syslog field is enabled and sensitive fields repeat in log entries.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"palo_alto","cpe":[{"product":"pan-os","vendor":"paloaltonetworks"}],"cvss":{"score":3.3,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"An information exposure through log file vulnerability where sensitive fields are recorded in the configuration log without masking on Palo Alto Networks PAN-OS software when the after-change-detail custom syslog field is enabled for configuration logs and the sensitive field appears multiple times in one log entry. The first instance of the sensitive field is masked but subsequent instances are left in clear text. This issue impacts: PAN-OS 8.1 versions earlier than PAN-OS 8.1.16; PAN-OS 9.0 versions earlier than PAN-OS 9.0.10; PAN-OS 9.1 versions earlier than PAN-OS 9.1.4.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"PAN-OS: Passwords may be logged in clear text when using after-change-detail custom syslog field for config logs","id":"CVE-2020-2043","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"paloaltonetworks:pan-os","products":["paloaltonetworks:pan-os"],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"PAN-OS: Passwords may be logged in clear text while storing operational command (op command) history","id":"CVE-2020-2044"},"packages":[],"prev":{"headline":"PAN-OS: Buffer overflow in the management web interface","id":"CVE-2020-2042"},"products":["PAN-OS"],"published":"2020-09-09","related":[{"cvss_score":10,"headline":"Palo Alto Networks PAN-OS Command Injection","id":"CVE-2024-3400","kev_date_added":"2024-04-12","published":"2024-04-12"},{"cvss_score":10,"headline":"Palo Alto Networks PAN-OS Authentication Bypass","id":"CVE-2020-2021","kev_date_added":"2022-03-25","published":"2020-06-29"},{"cvss_score":9.8,"headline":"Palo Alto Networks PAN-OS Remote Code Execution","id":"CVE-2017-15944","kev_date_added":"2022-08-18","published":"2017-12-11"},{"cvss_score":9.3,"headline":"Palo Alto Networks PAN-OS Out-of-bounds Write","id":"CVE-2026-0300","kev_date_added":"2026-05-06","published":"2026-05-06"},{"cvss_score":9.3,"headline":"Palo Alto Networks PAN-OS Management Interface Authentication Bypass","id":"CVE-2024-0012","kev_date_added":"2024-11-18","published":"2024-11-18"},{"cvss_score":9.2,"headline":"PHP Memory Corruption","id":"CVE-2026-109618","kev_date_added":"2026-10-26","published":"2026-10-21"},{"cvss_score":9.2,"headline":"PHP Stale Internal Request-State","id":"CVE-2026-109619","kev_date_added":"2026-10-26","published":"2026-10-21"}],"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-09-16","vendors":["Palo Alto Networks"]},"summary":"Attackers with log access can read clear-text passwords if the after-change-detail syslog field is enabled and sensitive fields repeat in log entries.","url":"https://insights.sbomify.com/CVE-2020-2043/"}