dbcve.org
FortiosOperating system · Fortinet

CVE-2023-44247

HIGH · 7.2 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to after 6.4.15 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 6.4 all versions may allow 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 vulnerability (CWE-415) in Fortinet FortiOS 6.4 allows an authenticated, privileged attacker to execute arbitrary code or commands by sending specially crafted HTTP or HTTPS requests. The vulnerability stems from improper memory management where freed memory is accessed and freed again, potentially leading to heap corruption and code execution.

MitigationApply available Fortinet patches for FortiOS 6.4; if no patch exists, minimize attack surface by restricting administrative access to trusted IP ranges and monitoring for suspicious admin activity.

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.2.0, <= 6.2.16>= 6.4.0, <= 6.4.15

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. Identify FortiOS version
    Run 'get system status' or 'diagnose system sysinfo' in the FortiOS CLI to obtain the firmware version
    Affected if Version is 6.2.0 through 6.2.16 OR 6.4.0 through 6.4.15
  2. Verify HTTP/HTTPS management is enabled
    Run 'show system interface' and check for 'set http 1' or 'set https 1' on the management interface in the CLI
    Affected if HTTP or HTTPS administrative access is enabled on any interface
  3. Confirm privileged admin accounts exist
    Run 'get admin user' in the CLI to list administrator accounts and their profile assignments
    Affected if Any administrative user with privileged access (such as super_admin or custom profiles with write access) is configured
  4. Check if admin interface is exposed externally
    Review interface configuration with 'show system interface' and verify which IP addresses are bound to management services via 'show system global'
    Affected if HTTP/HTTPS management is accessible from untrusted networks or interfaces with any-any firewall policies

A system is affected if it runs FortiOS 6.2.0-6.2.16 or 6.4.0-6.4.15 AND has HTTP/HTTPS administrative access enabled with at least one privileged admin account configured.

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 a release after 6.4.15
Interim mitigation

Apply available Fortinet patches for FortiOS 6.4; if no patch exists, minimize attack surface by restricting administrative access to trusted IP ranges and monitoring for suspicious admin activity.

Recommended fix Moderate confidence

FortiOS 7.0.x or later (7.2.x recommended); alternatively FortiOS 6.4.16 or later if 7.x is not feasible

  1. 1. Identify the current FortiOS version running on the Fortinet device using 'get system status' or through the web UI dashboard.
  2. 2. Confirm the version falls within the affected ranges: 6.2.0-6.2.16 or 6.4.0-6.4.15.
  3. 3. Download the latest FortiOS release from the Fortinet Customer Support Portal (https://support.fortinet.com) after upgrading to a fixed version.
  4. 4. Upload the firmware image to the FortiOS device via the web UI (System > Firmware) or CLI using 'execute firmware upgrade' or 'set firmware-file'.
  5. 5. After upgrade, verify the new version is installed and the device is operational using 'get system status'.
  6. 6. Confirm the running version no longer falls within the affected version ranges.
Caveat Upgrading major versions (6.x to 7.x) may introduce feature changes; review Fortinet release notes for compatibility and configuration adjustments before upgrading in production environments

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

Fix this in Fortios Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,620
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-44247 — 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-44247 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