CVE-2024-47570 Vulnerability Analysis & Exploit Details

CVE-2024-47570
Vulnerability Scoring

6.6
/10
High Risk

If left unpatched, CVE-2024-47570 could lead to major system disruptions or data loss.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: High
    High-level privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2024-47570 Details

Status: Analyzed

Last updated: 🕣 10 Dec 2025, 20:32 UTC
Originally published on: 🕕 09 Dec 2025, 18:15 UTC

Time between publication and last update: 1 days

CVSS Release: version 3

CVSS3 Source

psirt@fortinet.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H

CVE-2024-47570 Vulnerability Summary

CVE-2024-47570: 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).

Assessing the Risk of CVE-2024-47570

Access Complexity Graph

The exploitability of CVE-2024-47570 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2024-47570

The exploitability of CVE-2024-47570 is influenced by multiple factors. Security teams should analyze system configurations and apply appropriate countermeasures to mitigate threats.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2024-47570, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2024-47570, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2024-47570 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2024-47570 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2024-47570 can disrupt system operations, potentially causing complete denial of service (DoS).

CVE-2024-47570 References

External References

CWE Common Weakness Enumeration

CWE-532

CAPEC Common Attack Pattern Enumeration and Classification

  • Fuzzing for application mapping CAPEC-215 An attacker sends random, malformed, or otherwise unexpected messages to a target application and observes the application's log or error messages returned. The attacker does not initially know how a target will respond to individual messages but by attempting a large number of message variants they may find a variant that trigger's desired behavior. In this attack, the purpose of the fuzzing is to observe the application's log and error messages, although fuzzing a target can also sometimes cause the target to enter an unstable state, causing a crash.

Vulnerable Configurations

  • cpe:2.3:a:fortinet:fortiproxy:7.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortiproxy:7.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortiproxy:7.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortiproxy:7.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortiproxy:7.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortiproxy:7.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortiproxy:7.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortiproxy:7.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortiproxy:7.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortiproxy:7.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortiproxy:7.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortiproxy:7.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortiproxy:7.2.6:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortiproxy:7.2.6:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortiproxy:7.2.7:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortiproxy:7.2.7:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortiproxy:7.2.8:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortiproxy:7.2.8:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortiproxy:7.2.9:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortiproxy:7.2.9:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortiproxy:7.2.10:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortiproxy:7.2.10:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortiproxy:7.2.11:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortiproxy:7.2.11:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortiproxy:7.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortiproxy:7.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortiproxy:7.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortiproxy:7.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortiproxy:7.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortiproxy:7.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortiproxy:7.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortiproxy:7.4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortisase:24.1.37:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortisase:24.1.37:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortisra:1.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortisra:1.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortisra:1.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortisra:1.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortisra:1.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortisra:1.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:fortinet:fortisra:1.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:fortinet:fortisra:1.4.3:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.0.5:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.0.6:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.0.6:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.0.7:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.0.7:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.0.8:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.0.8:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.0.9:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.0.9:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.0.10:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.0.10:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.0.11:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.0.11:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.0.12:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.0.12:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.0.13:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.0.13:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.0.14:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.0.14:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.0.15:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.0.15:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.0.16:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.0.16:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.0.17:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.0.17:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.2.0:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.2.0:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.2.1:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.2.1:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.2.2:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.2.2:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.2.3:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.2.3:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.2.4:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.2.4:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.2.5:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.2.5:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.2.6:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.2.6:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.2.7:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.2.7:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.4.0:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.4.0:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.4.1:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.4.1:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.4.2:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.4.2:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortios:7.4.3:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortios:7.4.3:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortipam:1.0.0:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortipam:1.0.0:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortipam:1.0.1:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortipam:1.0.1:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortipam:1.0.2:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortipam:1.0.2:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortipam:1.0.3:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortipam:1.0.3:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortipam:1.1.0:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortipam:1.1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortipam:1.1.1:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortipam:1.1.1:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortipam:1.1.2:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortipam:1.1.2:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortipam:1.2.0:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortipam:1.2.0:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortipam:1.3.0:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortipam:1.3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortipam:1.3.1:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortipam:1.3.1:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortipam:1.4.0:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortipam:1.4.0:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortipam:1.4.1:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortipam:1.4.1:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortipam:1.4.2:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortipam:1.4.2:*:*:*:*:*:*:*
  • cpe:2.3:o:fortinet:fortipam:1.4.3:*:*:*:*:*:*:*
    cpe:2.3:o:fortinet:fortipam:1.4.3:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-47570: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-15170 – A security vulnerability has been detected in Advaya Softech GEMS ERP Portal up to 2.1. This affects an unknown part of the file /home.jsp?isError=...
  • CVE-2025-15169 – A weakness has been identified in BiggiDroid Simple PHP CMS 1.0. Affected by this issue is some unknown functionality of the file /admin/editsite.p...
  • CVE-2025-52691 – Successful exploitation of the vulnerability could allow an unauthenticated attacker to upload arbitrary files to any location on the mail server, ...
  • CVE-2025-15168 – A vulnerability was identified in itsourcecode Student Management System 1.0. Affected is an unknown function of the file /statistical.php. Such ma...
  • CVE-2025-15167 – A vulnerability was determined in itsourcecode Online Cake Ordering System 1.0. This impacts an unknown function of the file /detailtransac.php. Th...