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-45324A use of externally-controlled format string vulnerability [CWE-134] in FortiOS version 7.4.0 through 7.4.4, version 7.2.0 through 7.2.9,…

Description

A use of externally-controlled format string vulnerability [CWE-134] in FortiOS version 7.4.0 through 7.4.4, version 7.2.0 through 7.2.9, version 7.0.0 through 7.0.15 and before 6.4.15, FortiProxy version 7.4.0 through 7.4.6, version 7.2.0 through 7.2.12 and before 7.0.19, FortiPAM version 1.4.0 through 1.4.2 and before 1.3.1, FortiSRA version 1.4.0 through 1.4.2 and before 1.3.1 and FortiWeb version 7.4.0 through 7.4.5, version 7.2.0 through 7.2.10 and before 7.0.10 allows a privileged attacker to execute unauthorized code or commands via specially crafted HTTP or HTTPS commands.

Timeline

  1. ID reserved

    By fortinet

  2. · 7 months later

    Published

  3. · 12 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-45324, by who scored it
Scored byCVSSScoreVector
fortinetCNA (assigner)3.1High7.0CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/E:F/RL:U/RC:C
NVDNVD · Analyzed3.1High7.2CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.73% · top 45% of all CVEs (13 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: High 7.0.

Affected products

  • Fortinet · FortiPAM

    • affected 1.4.0 – ≤ 1.4.2
    • 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 · FortiWeb

    • affected 7.6.0
    • affected 7.4.0 – ≤ 7.4.5
    • affected 7.2.0 – ≤ 7.2.10
    • affected 7.0.0 – ≤ 7.0.10

  • Fortinet · FortiProxy

    • affected 7.6.0
    • affected 7.4.0 – ≤ 7.4.6
    • affected 7.2.0 – ≤ 7.2.12
    • affected 7.0.0 – ≤ 7.0.19

  • Fortinet · FortiSRA

    • affected 1.4.0 – ≤ 1.4.2

  • Fortinet · FortiOS

    • affected 7.4.0 – ≤ 7.4.4
    • affected 7.2.0 – ≤ 7.2.9
    • affected 7.0.0 – ≤ 7.0.15
    • affected 6.4.0 – ≤ 6.4.15
    • affected 6.2.0 – ≤ 6.2.16

What to do

Solution: Upgrade to FortiPAM version 1.5.0 or above Upgrade to FortiPAM version 1.4.3 or above Upgrade to upcoming FortiPAM version 1.3.2 or above Upgrade to FortiProxy version 7.6.1 or above Upgrade to FortiProxy version 7.4.7 or above Upgrade to FortiProxy version 7.2.13 or above Upgrade to FortiProxy version 7.0.20 or above Upgrade to FortiOS version 7.6.0 or above Upgrade to FortiOS version 7.4.5 or above Upgrade to FortiOS version 7.2.10 or above Upgrade to FortiOS version 7.0.16 or above Upgrade to FortiOS version 6.4.16 or above Upgrade to FortiOS version 6.2.17 or above Upgrade to upcoming FortiAuthenticator version 7.0.0 or above Upgrade to FortiWeb version 7.6.1 or above Upgrade to FortiWeb version 7.4.6 or above Upgrade to FortiWeb version 7.2.11 or above Upgrade to FortiWeb version 7.0.11 or above Fortinet remediated this issue in FortiSASE version 24.4.b1 and hence customers do not need to perform any action. Upgrade to FortiSRA version 1.5.0 or above Upgrade to FortiSRA version 1.4.3 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-45324 badge
[![CVE-2024-45324](https://cveledger.app/badge/CVE-2024-45324.svg)](https://cveledger.app/cve/CVE-2024-45324)

Record last updated .