Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-47570An 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…

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).

Timeline

  1. ID reserved

    By fortinet

  2. · 15 months later

    Published

  3. · 3 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-47570, by who scored it
Scored byCVSSScoreVector
fortinetCNA (assigner)3.1Medium6.3CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:C
NVDNVD · Analyzed3.1Medium6.6CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.43% · top 62% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.3.

Affected products

  • Fortinet · FortiSASE

    • affected 24.1.10
  • Fortinet · FortiProxy

    • affected 7.4.0 – ≤ 7.4.3
    • affected 7.2.0 – ≤ 7.2.11
  • Fortinet · FortiSRA

    • affected 1.4.0 – ≤ 1.4.3
  • Fortinet · FortiPAM

    • affected 1.4.0 – ≤ 1.4.3
    • affected 1.3.0 – ≤ 1.3.1
    • affected 1.2.0
    • affected 1.1.0 – ≤ 1.1.2
    • affected 1.0.0 – ≤ 1.0.3
  • Fortinet · FortiOS

    • affected 7.4.0 – ≤ 7.4.3
    • affected 7.2.0 – ≤ 7.2.7
    • affected 7.0.4 – ≤ 7.0.18

What to do

Solution: Fortinet remediated this issue in FortiSASE version 24.1.c and hence customers do not need to perform any action. Upgrade to FortiProxy version 7.4.4 or above Upgrade to FortiProxy version 7.2.12 or above Upgrade to FortiSRA version 1.6.0 or above Upgrade to FortiSRA version 1.5.0 or above Upgrade to FortiPAM version 1.6.0 or above Upgrade to FortiPAM version 1.5.0 or above Upgrade to FortiOS version 7.6.0 or above Upgrade to FortiOS version 7.4.4 or above Upgrade to FortiOS version 7.2.8 or above

References

References1

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-47570 badge
[![CVE-2024-47570](https://cveledger.app/badge/CVE-2024-47570.svg)](https://cveledger.app/cve/CVE-2024-47570)

Record last updated .