● Critical · CVSS 9.8

How to Fix CVE-2023-33308: Execute unauthorized code or commands in FortiProxy

Q: Is CVE-2023-33308 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That can change, so monitor the advisory and KEV catalog.

Q: How severe is CVE-2023-33308?

CVSS rates it 9.8 (Critical). Treat it accordingly in your prioritisation queue.

Q: Do I have to take FortiProxy offline to apply the patch?

That depends on your deployment topology. For high-availability or clustered setups you can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

⚡ At a glance


Severity	CVSS 9.8, Critical
Actively exploited?	No
Affected	Fortinet FortiProxy (<= 7.2.2, <= 7.0.9); Fortinet FortiOS (<= 7.2.3, <= 7.0.10)
Fixed in	Newer than 7.2.2 (per vendor advisory)
Type (CWE)	CWE-121: Execute unauthorized code or commands

What is CVE-2023-33308?

A stack-based overflow vulnerability [CWE-124] in Fortinet FortiOS version 7.0.0 through 7.0.10 and 7.2.0 through 7.2.3 and FortiProxy version 7.0.0 through 7.0.9 and 7.2.0 through 7.2.2 allows a remote unauthenticated attacker to execute arbitrary code or command via crafted packets reaching proxy policies or firewall policies with proxy mode alongside deep or full packet inspection.

In short, a successful attacker gets remote code execution on the affected system. No confirmed in-the-wild exploitation is listed in CISA KEV at the time of writing, but the CVSS rating still warrants prompt patching.

Am I affected?

Check whether you run Fortinet FortiProxy in your environment, then compare your installed version against the Affected row above.


get system status

How to fix CVE-2023-33308

Read the official vendor advisory linked at the bottom of this page and identify the exact patched build for your release train.
Download the patched build of FortiProxy from the vendor's support portal. Use only signed images from the vendor.
Back up configuration and, where supported, take a snapshot of the host or appliance before you start.
Apply the update following the vendor's documented procedure. For clustered or high-availability deployments, patch the standby node first, fail over, then patch the previously active node.
Restart the affected service or appliance if the upgrade procedure requires it.
Re-run the version check from the previous section and confirm the build matches the fixed release.

Apply the iOS / iPadOS update


# Check the current iOS build on a tethered device (libimobiledevice)
ideviceinfo -k ProductVersion
ideviceinfo -k BuildVersion

# Required iOS / iPadOS build is listed in the vendor advisory: https://fortiguard.com/psirt/FG-IR-23-183
# On-device: Settings -> General -> Software Update -> Download and Install


# Vendor advisory: https://fortiguard.com/psirt/FG-IR-23-183
# Confirm fleet iOS devices have updated (Intune example)
Connect-MgGraph -Scopes Device.Read.All
Get-MgDeviceManagementManagedDevice -Filter "operatingSystem eq 'iOS'" |
  Where-Object { $_.OSVersion -lt "<fixed-version-from-advisory>" } |
  Select-Object DeviceName, OSVersion, UserPrincipalName

Verify the fix landed


# 1. Confirm the running version matches the fixed-in version from the advisory:
#    https://fortiguard.com/psirt/FG-IR-23-183
#    Use the platform-specific version probe above.

# 2. Re-scan with your vulnerability scanner (Nessus, Qualys, Tenable, OpenVAS).
#    The scanner should no longer flag CVE-2023-33308 on the patched target.

# 3. Inspect recent service / kernel logs for crash loops or rollback events.
journalctl -u <service> --since "10 minutes ago"
dmesg --since "10 minutes ago"

If you can't patch immediately

If patching has to wait, block external access to the affected service at the firewall and restrict to a small, audited management network. Enable any vendor-recommended detection rules or WAF signatures listed in the advisory. None of these are a substitute for the patch.

How to verify the fix worked

Confirm the running build of FortiProxy matches the fixed version listed by the vendor. Re-run any vulnerability scanner you used previously and confirm the finding for CVE-2023-33308 has cleared. Where the vendor publishes a detection rule or IOCs, sweep your logs for evidence of pre-patch exploitation.

Why this CVE matters

CVSS 9.8 (Critical) reflects either remote, unauthenticated exploitability, full impact on confidentiality / integrity / availability, or both. Most internal SLAs map a Critical rating to a 7-to-15 day patch deadline regardless of in-the-wild reports. Public-facing instances should be patched on the shorter end of that window.

Monitoring and detection

After you apply the patch, treat the affected component as a known-good baseline and watch for regression. Concrete steps:

Re-run your usual vulnerability scanner on a weekly cycle for the next month and confirm the finding stays clear.
Forward the affected component's logs to your SIEM, then write a rule for any failed-auth burst or unusual configuration change on the component.
If the vendor advisory lists indicators of compromise, hash patterns, or specific log strings, build detection rules in your SIEM around them and back-search the last 90 days of logs.
Tag the patched build in your CMDB so future audits can confirm it stayed patched through any rebuild or re-image.

Defensive hardening beyond the patch

Patching closes this specific CVE. A few common-sense controls reduce the blast radius of the next one in the same component:

Restrict management interface (HTTPS / SSH) access to a small administrative subnet using interface ACLs or trusted-host lists.
Enable AAA logging and forward to your SIEM. Alert on any successful admin login from outside the trusted subnet.
Where the vendor supports it, enable two-factor authentication for admin accounts.
Schedule quarterly password rotation for any local admin or break-glass accounts on the appliance.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2023-40714: FortiSIEM (Bundle Sibling) — FortiSIEM (Bundle Sibling)
How to Fix CVE-2023-34992: Execute unauthorized code or commands in FortiSIEM — Execute unauthorized code or commands in FortiSIEM
How to Fix CVE-2023-48788: SQL Injection in FortiClientEMS , SQL Injection in FortiClientEMS

Is CVE-2023-33308 being actively exploited?