Safeguard
Vulnerability Analysis•

CVE-2023-29180: High DoS in Fortinet FortiOS SSL-VPN

CVE-2023-29180 is a High (CVSS 7.5) NULL pointer dereference that can crash the FortiOS SSL-VPN daemon. Upgrade FortiOS or FortiProxy to the fixed release.

Safeguard Security Team
3 min read

CVE-2023-29180 is a high severity (CVSS 7.5) NULL pointer dereference in Fortinet FortiOS and FortiProxy. A remote, unauthenticated attacker can crash the SSL-VPN daemon with crafted HTTP requests. Fortinet's fixes are FortiOS 7.2.5, 7.0.12, 6.4.13, 6.2.15 and 6.0.17, and FortiProxy 7.2.4, 7.0.11 and 2.0.13.

What's affected

FortiGuard advisory FG-IR-23-111 lists these affected and fixed versions.

  • FortiOS 7.4: not affected.
  • FortiOS 7.2.0 through 7.2.4: upgrade to 7.2.5 or above.
  • FortiOS 7.0.0 through 7.0.11: upgrade to 7.0.12 or above.
  • FortiOS 6.4.0 through 6.4.12: upgrade to 6.4.13 or above.
  • FortiOS 6.2.0 through 6.2.14: upgrade to 6.2.15 or above.
  • FortiOS 6.0.0 through 6.0.16: upgrade to 6.0.17 or above.
  • FortiProxy 7.2.0 through 7.2.3: upgrade to 7.2.4 or above.
  • FortiProxy 7.0.0 through 7.0.10: upgrade to 7.0.11 or above.
  • FortiProxy 2.0.0 through 2.0.12: upgrade to 2.0.13 or above.
  • FortiProxy 1.2, 1.1 and 1.0, all versions: migrate to a fixed release.

The NVD record's version ranges match the advisory for the FortiOS and FortiProxy lines above.

How to check if you're exposed

On a FortiGate or FortiProxy, check the running version from the CLI:

get system status

Compare the Version line to the table in the advisory. You can also read it under the dashboard system information widget. This is a device or appliance issue, not a package you pull from a registry, so a dependency scan will not see it. Safeguard's free in-browser scan at https://gold.safeguard.sh/scan reads dependency manifests and will not detect firmware running on hardware. Use your asset inventory instead.

What to do now

  1. Find every FortiGate and FortiProxy unit and note its version.
  2. Upgrade to the fixed release for your branch. Fortinet publishes an upgrade path tool at https://docs.fortinet.com/upgrade-tool.
  3. If you cannot upgrade yet, check whether SSL-VPN is enabled at all. The advisory describes the crash in the SSL-VPN daemon, so a unit with the feature off has less exposure.
  4. Move FortiProxy 1.x units to a supported release, since Fortinet gives no patch for those lines.

Why it matters

The advisory describes a CWE-476 flaw in the SSL-VPN service, which Fortinet calls Null pointer dereference in sslvnd. Crafted HTTP requests send the process down a path where it uses a pointer that was never set, and it crashes. The impact listed is denial of service.

That matters because the SSL-VPN service often fronts remote access for a whole organization. A crash can drop users until the daemon restarts. FortiGuard marks the issue High with a temporal score of 7.3, lists it as unauthenticated and internally discovered, and says it is not known to be exploited. This CVE is not on the CISA KEV list either.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Is this exploited in the wild?

Fortinet marks Known Exploited as No on the advisory, and the CVE is not in the CISA KEV catalogue.

Does it need a login?

No. The advisory lists the attack type as unauthenticated.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.