dbcve.org
FortiosOperating system · Fortinet

CVE-2023-37930

HIGH · 8.8 CVSS v3.1 Published 2025-04-08
Fix available
A fix is available. Upgrade to 6.4.15 / 7.0.13 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Multiple issues including the use of uninitialized ressources [CWE-908] and excessive iteration [CWE-834] vulnerabilities vulnerability in Fortinet allows a VPN user to corrupt memory potentially leading to code or commands execution via specifically crafted 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 · moderate confidence

Fortinet VPN contains memory corruption vulnerabilities (CWE-908 uninitialized resources, CWE-834 excessive iteration) that allow authenticated VPN users to corrupt memory via specifically crafted requests, potentially achieving code or command execution.

MitigationApply the vendor-supplied patch for Fortinet VPN; coordinate maintenance window for update deployment and verify VPN functionality post-patch.

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.7, < 6.4.15>= 7.0.1, < 7.0.13>= 7.2.0, < 7.2.6= 7.4.0
FortiproxyApplication
Affected:>= 7.0.0, < 7.0.13>= 7.2.0, < 7.2.7

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 firmware version
    Run `get system status` on the FortiGate CLI or check System > Firmware in the web UI. Look for the 'FortiOS' or 'FortiGate' version field.
    Affected if The version falls within: 6.4.7 to 6.4.14, 7.0.1 to 7.0.12, 7.2.0 to 7.2.5, or equals 7.4.0
  2. Identify Fortiproxy version
    Run `get system status` on the Fortiproxy device or check the web UI under System > Firmware. Note the version displayed.
    Affected if The version falls within: 7.0.0 to 7.0.12, or 7.2.0 to 7.2.6
  3. Confirm SSL-VPN is enabled
    Run `get vpn ssl settings` or `show vpn ssl` in the FortiGate CLI. Look for 'set status enable' or verify port configuration.
    Affected if SSL-VPN is currently enabled and listening (status shows enabled)
  4. Verify SSL-VPN web mode or full tunnel access
    Run `show vpn ssl` and inspect the configuration for 'set mode {web| tunnel}' and any defined user groups or policies allowing VPN access.
    Affected if SSL-VPN is configured with any user authentication methods (local users, LDAP, RADIUS, or groups)

You are affected if your FortiOS version is 6.4.7-6.4.14, 7.0.1-7.0.12, 7.2.0-7.2.5, or 7.4.0, OR your Fortiproxy version is 7.0.0-7.0.12 or 7.2.0-7.2.6, AND SSL-VPN is enabled with authentication 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 6.4.15 / 7.0.13 / 7.2.6 or later
Fixed in 6.4.157.0.137.2.6
Interim mitigation

Apply the vendor-supplied patch for Fortinet VPN; coordinate maintenance window for update deployment and verify VPN functionality post-patch.

Recommended fix High confidence

FortiOS: 6.4.15+, 7.0.13+, 7.2.6+, 7.4.1+ | FortiProxy: 7.0.13+, 7.2.7+

  1. 1. Identify the current FortiOS or FortiProxy version running on your device via the Web UI (System > Firmware) or CLI (get system status)
  2. 2. Based on your current version branch, plan the upgrade to the minimum fixed version: For FortiOS 6.4.x upgrade to 6.4.15 or later; For FortiOS 7.0.x upgrade to 7.0.13 or later; For FortiOS 7.2.x upgrade to 7.2.6 or later; For FortiOS 7.4.x upgrade to 7.4.1 or later; For FortiProxy 7.0.x upgrade to 7.0.13 or later; For FortiProxy 7.2.x upgrade to 7.2.7 or later
  3. 3. Download the appropriate firmware image from the Fortinet Customer Service & Support portal (support.fortinet.com)
  4. 4. Back up the current device configuration via CLI (execute backup config) or Web UI
  5. 5. Upload and install the new firmware via System > Firmware in the Web UI or via CLI (execute system firmware upgrade)
  6. 6. After reboot, verify the upgrade was successful and confirm the new version via get system status
  7. 7. Validate that VPN functionality and other critical services are operating normally
Caveat Major version upgrades (e.g., 6.4 to 7.0) may introduce configuration or behavioral changes; review release notes and test in a non-production environment first

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
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
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,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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