dbcve.org
FortiproxyApplication · Fortinet

CVE-2023-33308

CRITICAL · 9.8 CVSS v3.1 Published 2023-07-26
Fix available
A fix is available. Upgrade to after 7.2.3 or later.
See remediation →
100/100
Remediation priority · Urgent
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 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.

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 stack-based buffer overflow (CWE-124) in FortiOS 7.0.0-7.0.10 and 7.2.0-7.2.3 and FortiProxy 7.0.0-7.0.9 and 7.2.0-7.2.2 allows remote unauthenticated attackers to execute arbitrary code via crafted packets reaching proxy policies or firewall policies with proxy mode and deep/full packet inspection enabled.

MitigationUpgrade to FortiOS 7.0.11/7.2.4 or later or FortiProxy 7.0.10/7.2.3 or later; alternatively, disable proxy policies and deep/full packet inspection as a compensating control until patching is feasible.

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:>= 7.0.0, <= 7.0.9= 7.2.0= 7.2.1= 7.2.2
FortiosOperating system
Affected:>= 7.0.0, <= 7.0.10>= 7.2.0, <= 7.2.3

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Check FortiOS version
    Run command: get system status or execute 'fortios -v' via CLI to retrieve the installed FortiOS version
    Affected if Version is 7.0.0 through 7.0.10 or 7.2.0 through 7.2.3
  2. Check FortiProxy version
    Run command: get system status or execute 'fortiproxy -v' via CLI to retrieve the installed FortiProxy version
    Affected if Version is 7.0.0 through 7.0.9 or 7.2.0 through 7.2.2
  3. Identify proxy policies
    Run command: get firewall proxy-policy or view config firewall proxy-policy in FortiOS/FortiProxy CLI
    Affected if Any proxy policies are configured and active
  4. Identify firewall policies with proxy mode
    Run command: get firewall policy or view config firewall policy to check if any policies have 'proxy' set as the explicit proxy type or enable-proxy set to enable explicit web proxy
    Affected if Firewall policies with proxy mode enabled exist
  5. Check deep/full packet inspection on policies
    Run command: get firewall policy and inspect the 'inspection-mode' or 'ipsensor' field, or view config firewall policy to check if 'deep-inspection' is enabled for the relevant policies
    Affected if Deep inspection or full SSL inspection is enabled on firewall policies that use proxy mode

Environment is affected if running a FortiOS version 7.0.0-7.0.10 or 7.2.0-7.2.3, or FortiProxy version 7.0.0-7.0.9 or 7.2.0-7.2.2, AND either proxy policies exist OR firewall policies with proxy mode have deep/full packet inspection enabled.

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 7.2.3
Interim mitigation

Upgrade to FortiOS 7.0.11/7.2.4 or later or FortiProxy 7.0.10/7.2.3 or later; alternatively, disable proxy policies and deep/full packet inspection as a compensating control until patching is feasible.

Recommended fix High confidence

FortiOS 7.0.11 or later / FortiOS 7.2.4 or later / FortiProxy 7.0.10 or later / FortiProxy 7.2.3 or later

  1. 1. Identify the currently installed FortiOS or FortiProxy version using 'get system status' or 'get system interface' CLI command
  2. 2. For FortiOS 7.0.x deployments: upgrade to FortiOS 7.0.11 or later
  3. 3. For FortiOS 7.2.x deployments: upgrade to FortiOS 7.2.4 or later
  4. 4. For FortiProxy 7.0.x deployments: upgrade to FortiProxy 7.0.10 or later
  5. 5. For FortiProxy 7.2.x deployments: upgrade to FortiProxy 7.2.3 or later
  6. 6. After upgrade, verify the new version is installed using 'get system status'
  7. 7. Test that proxy policies and firewall policies with deep inspection continue to function correctly
Caveat Review Fortinet release notes for 7.0.11, 7.2.4, 7.0.10, and 7.2.3 for any configuration or behavioral changes that may affect your deployment

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

Fix this in Fortiproxy Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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