{"answers":{"affected":"It affects 5 products.","exploited":"There is no known exploitation of CVE-2024-47570 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-47570 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-47570 is a medium-severity vulnerability in Fortinet Fortios, published on 9 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-47570 and fix it if it is affected.\n\nWhat it is: CVE-2024-47570 is a medium-severity vulnerability in Fortinet Fortios, published on 9 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-47570 in the wild and no public exploit code.\n\nAffected product: Fortinet Fortios. 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-2024-47570/ (Markdown: https://insights.sbomify.com/CVE-2024-47570/index.md)","id":"CVE-2024-47570","markdown":"https://insights.sbomify.com/CVE-2024-47570/index.md","name":"CVE-2024-47570","record":{"aliases":["GHSA-fgjc-2w92-q899"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Fortinet network security","requires_auth":"high_privilege","summary":"A read-only administrator can retrieve other administrators' API tokens from REST API logs if logging is enabled, potentially leading to account takeover.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortios","vendor":"fortinet"},{"product":"fortipam","vendor":"fortinet"},{"product":"fortiproxy","vendor":"fortinet"},{"product":"fortisase","vendor":"fortinet"},{"product":"fortisra","vendor":"fortinet"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:C","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"An insertion of sensitive information into log file vulnerability [CWE-532] in FortiOS 7.4.0 through 7.4.3, 7.2.0 through 7.2.7, 7.0 all versions; FortiProxy 7.4.0 through 7.4.3, 7.2.0 through 7.2.11; FortiPAM 1.4 all versions, 1.3 all versions, 1.2 all versions, 1.1 all versions, 1.0 all versions and FortiSRA 1.4 all versions may allow a read-only administrator to retrieve API tokens of other administrators via observing REST API logs, if REST API logging is enabled (non-default configuration).","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":"Information disclosure in FortiOS","id":"CVE-2024-47570","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"fortinet:fortios","products":["fortinet:fortios","fortinet:fortiproxy"],"type":"information_disclosure","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Use after free in FortiManager","id":"CVE-2024-47571"},"packages":[],"prev":{"headline":"Information disclosure in FortiMail","id":"CVE-2024-47569"},"products":["FortiOS","FortiPAM","FortiProxy","FortiSASE","FortiSRA"],"published":"2025-12-09","related":[{"cvss_score":9.8,"headline":"Fortinet Multiple Products Format String","id":"CVE-2024-23113","kev_date_added":"2024-10-09","published":"2024-02-15"},{"cvss_score":9.8,"headline":"Fortinet Multiple Products Authentication Bypass","id":"CVE-2022-40684","kev_date_added":"2022-10-11","published":"2022-10-18"},{"cvss_score":9.6,"headline":"Fortinet FortiOS and FortiProxy Authentication Bypass","id":"CVE-2024-55591","kev_date_added":"2025-01-14","published":"2025-01-14"},{"cvss_score":9.6,"headline":"Fortinet FortiOS Out-of-Bound Write","id":"CVE-2024-21762","kev_date_added":"2024-02-09","published":"2024-02-09"},{"cvss_score":9.3,"headline":"Fortinet FortiOS Heap-Based Buffer Overflow","id":"CVE-2022-42475","kev_date_added":"2022-12-13","published":"2023-01-02"},{"cvss_score":9.2,"headline":"Fortinet FortiOS and FortiProxy SSL-VPN Heap-Based Buffer Overflow","id":"CVE-2023-27997","kev_date_added":"2023-06-13","published":"2023-06-13"},{"cvss_score":9.1,"headline":"Fortinet Multiple Products Improper Verification of Cryptographic Signature","id":"CVE-2025-59718","kev_date_added":"2025-12-16","published":"2025-12-09"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["Fortinet"]},"summary":"A read-only administrator can retrieve other administrators' API tokens from REST API logs if logging is enabled, potentially leading to account takeover.","url":"https://insights.sbomify.com/CVE-2024-47570/"}