dbcve.org
FortiosOperating system · Fortinet

CVE-2023-45584

HIGH · 7.2 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 7.0.13 / 7.0.14 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A double free vulnerability [CWE-415] vulnerability in Fortinet FortiOS 7.4.0, FortiOS 7.2.0 through 7.2.5, FortiOS 7.0.0 through 7.0.12, FortiOS 6.4 all versions, FortiPAM 1.1 all versions, FortiPAM 1.0 all versions, FortiProxy 7.4.0 through 7.4.1, FortiProxy 7.2.0 through 7.2.7, FortiProxy 7.0.0 through 7.0.13 allows a privileged attacker to execute code or commands via crafted HTTP or HTTPs requests.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A double free (CWE-415) memory corruption vulnerability in FortiOS and FortiProxy allows a privileged attacker to trigger the same memory pointer to be freed twice via crafted HTTP/HTTPS requests, leading to heap corruption that can be leveraged for arbitrary code execution.

MitigationApply Fortinet's vendor patches for the affected FortiOS/FortiProxy versions. Until patches are applied, restrict administrative interface access to trusted IPs only and monitor for anomalous HTTP/HTTPS traffic patterns.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FortiosOperating system
Affected:>= 6.4.0, < 7.0.13>= 7.2.0, < 7.2.6= 7.4.0
FortipamOperating system
Affected:>= 1.0.0, <= 1.1.2
FortiproxyApplication
Affected:>= 7.0.0, < 7.0.14>= 7.2.0, < 7.2.8>= 7.4.0, < 7.4.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check FortiOS version
    Run 'get system status' via CLI or check the GUI under System > Firmware. Compare the displayed version against the affected ranges: 6.4.0 to 7.0.12, 7.2.0 to 7.2.5, or 7.4.0
    Affected if The installed version falls within any of the affected ranges listed in the CVE (>=6.4.0,<7.0.13; >=7.2.0,<7.2.6; =7.4.0)
  2. Check FortiProxy version
    Run 'get system status' or 'get system information' via CLI on the FortiProxy device. Compare against affected ranges: 7.0.0 to 7.0.13, 7.2.0 to 7.2.7, or 7.4.0 to 7.4.1
    Affected if The installed version falls within any of the affected FortiProxy ranges (>=7.0.0,<7.0.14; >=7.2.0,<7.2.8; >=7.4.0,<7.4.2)
  3. Check Fortipam version
    Run 'get system status' or check the FortiPAM management interface for the installed version. Compare against 1.0.0 to 1.1.2
    Affected if Fortipam version is between 1.0.0 and 1.1.2 inclusive
  4. Verify HTTP/HTTPS management interface status
    Run 'get system interface' and 'show system interface' to list interfaces. Check if 'set http' or 'set https' is enabled on WAN-facing or accessible interfaces. Alternatively, check via GUI under Network > Interfaces
    Affected if HTTP or HTTPS administrative access is enabled on an interface reachable by the attacker (particularly WAN/external-facing interfaces)
  5. Confirm administrative access restriction
    Review firewall policies and interface access lists. Check if admin access is limited to trusted IPs via 'config system interface' then 'edit <interface>' then 'set allowaccess' to see permitted management protocols and source IPs
    Affected if Administrative interfaces (HTTP/HTTPS) are open to untrusted or all source IPs rather than limited to specific trusted management networks

You are affected if your FortiOS, FortiProxy, or Fortipam version falls within the listed vulnerable ranges AND the HTTP/HTTPS administrative interface is accessible to the attacker (authenticated/privileged user).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.0.13 / 7.0.14 / 7.2.6 or later
Fixed in 7.0.137.0.147.2.6
Interim mitigation

Apply Fortinet's vendor patches for the affected FortiOS/FortiProxy versions. Until patches are applied, restrict administrative interface access to trusted IPs only and monitor for anomalous HTTP/HTTPS traffic patterns.

Recommended fix High confidence

FortiOS: 7.4.1, 7.2.6, or 7.0.13 (or later); FortiProxy: 7.4.2, 7.2.8, or 7.0.14 (or later); FortiPAM: contact Fortinet for fixed release

  1. 1. Identify the Fortinet product (FortiOS, FortiPAM, or FortiProxy) and current version running in your environment
  2. 2. For FortiOS 7.4.0: Upgrade to FortiOS 7.4.1 or later
  3. 3. For FortiOS 7.2.0-7.2.5: Upgrade to FortiOS 7.2.6 or later
  4. 4. For FortiOS 7.0.0-7.0.12: Upgrade to FortiOS 7.0.13 or later
  5. 5. For FortiOS 6.4.x: Upgrade to a supported FortiOS 7.x branch (7.0.13+, 7.2.6+, or 7.4.1+) as FortiOS 6.4 is end-of-life
  6. 6. For FortiPAM 1.0.x and 1.1.x: Contact Fortinet support for the fixed release as explicit version not specified in advisory
  7. 7. For FortiProxy 7.4.0-7.4.1: Upgrade to FortiProxy 7.4.2 or later
  8. 8. For FortiProxy 7.2.0-7.2.7: Upgrade to FortiProxy 7.2.8 or later
Caveat Upgrading across major FortiOS branches (e.g., 6.4 to 7.x) may introduce configuration or feature changes; review Fortinet upgrade guides and release notes for your specific path

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortios Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-45584 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-45584 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data