dbcve.org
FortiproxyApplication · Fortinet

CVE-2023-29180

HIGH · 7.5 CVSS v3.1 Published 2024-02-22
Fix available
A fix is available. Upgrade to 2.0.13 / 6.0.17 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 null pointer dereference in Fortinet FortiOS version 7.2.0 through 7.2.4, 7.0.0 through 7.0.11, 6.4.0 through 6.4.12, 6.2.0 through 6.2.14, 6.0.0 through 6.0.16, FortiProxy 7.2.0 through 7.2.3, 7.0.0 through 7.0.10, 2.0.0 through 2.0.12, 1.2.0 through 1.2.13, 1.1.0 through 1.1.6, 1.0.0 through 1.0.7 allows attacker to denial of service via specially crafted HTTP 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 null pointer dereference vulnerability exists in FortiOS and FortiProxy's HTTP request handling. The flaw is triggered by specially crafted HTTP requests sent to the affected systems, causing the process to dereference a null pointer and crash, resulting in denial of service.

MitigationApply the vendor-supplied patches: FortiOS 7.2.5+, 7.0.12+, 6.4.13+, 6.2.15+, 6.0.17+ and FortiProxy 7.2.4+, 7.0.11+, 2.0.13+, 1.2.14+, 1.1.7+, 1.0.8+. As interim mitigation, restrict HTTP access to trusted sources or place behind a WAF.

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
FortiproxyApplication
Affected:>= 1.0.0, <= 1.0.7>= 1.1.0, <= 1.1.6>= 1.2.0, <= 1.2.13>= 2.0.0, < 2.0.13>= 7.0.0, < 7.0.11>= 7.2.0, < 7.2.4
FortiosOperating system
Affected:>= 6.0.0, < 6.0.17>= 6.2.0, < 6.2.15>= 6.4.0, < 6.4.13>= 7.0.0, < 7.0.12>= 7.2.0, < 7.2.5

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the product type
    Run 'get system status' on the CLI or check the web UI dashboard to confirm whether the device runs FortiOS or FortiProxy
    Affected if The device is not FortiOS or FortiProxy (not affected)
  2. Retrieve the firmware version
    Run 'get system status' on the CLI or view the firmware version in the web UI under Dashboard > System Information
    Affected if The version cannot be determined or is not FortiOS/FortiProxy
  3. Compare FortiOS version against affected ranges
    If running FortiOS, check if version falls within: 6.0.0-6.0.16, 6.2.0-6.2.14, 6.4.0-6.4.12, 7.0.0-7.0.11, or 7.2.0-7.2.4
    Affected if The installed FortiOS version matches any of these ranges
  4. Compare FortiProxy version against affected ranges
    If running FortiProxy, check if version falls within: 1.0.0-1.0.7, 1.1.0-1.1.6, 1.2.0-1.2.13, 2.0.0-2.0.12, 7.0.0-7.0.10, or 7.2.0-7.2.3
    Affected if The installed FortiProxy version matches any of these ranges
  5. Verify HTTP management interface exposure
    Confirm whether the FortiOS/FortiProxy web UI (HTTP/HTTPS on port 443 or 80) is accessible from untrusted networks by reviewing interface bindings in 'config system interface' and policies allowing HTTP/HTTPS traffic
    Affected if The HTTP management interface is exposed to untrusted networks and the version is vulnerable

You are affected if the device runs a vulnerable FortiOS or FortiProxy version within the affected ranges AND its HTTP interface is reachable from attack vectors.

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 2.0.13 / 6.0.17 / 6.2.15 or later
Fixed in 2.0.136.0.176.2.15
Interim mitigation

Apply the vendor-supplied patches: FortiOS 7.2.5+, 7.0.12+, 6.4.13+, 6.2.15+, 6.0.17+ and FortiProxy 7.2.4+, 7.0.11+, 2.0.13+, 1.2.14+, 1.1.7+, 1.0.8+. As interim mitigation, restrict HTTP access to trusted sources or place behind a WAF.

Recommended fix High confidence

FortiOS: 6.0.17+, 6.2.15+, 6.4.13+, 7.0.12+, or 7.2.5+ | FortiProxy: 1.0.8+, 1.1.7+, 1.2.14+, 2.0.13+, or 7.2.4+

  1. Identify the current FortiOS or FortiProxy version running in your environment using the web UI or CLI command 'get system status'
  2. For FortiOS: Determine if your version is in an affected range (6.0.0-6.0.16, 6.2.0-6.2.14, 6.4.0-6.4.12, or 7.0.0-7.0.11)
  3. For FortiProxy: Determine if your version is in an affected range (1.0.0-1.0.7, 1.1.0-1.1.6, 1.2.0-1.2.13, or 2.0.0-2.0.12)
  4. Download the appropriate fixed firmware version from Fortinet's support portal at https://support.fortinet.com/
  5. Back up the current configuration before upgrading
  6. Upload and install the new firmware via the FortiOS/FortiProxy web UI (System > Firmware) or CLI
  7. After upgrade, verify the version matches the fixed release and confirm the system is functioning normally
Caveat Standard firmware upgrade - review Fortinet release notes for specific version for any minor compatibility notes or known issues before upgrading

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

Fix this in Fortiproxy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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