dbcve.org
FortiproxyApplication · Fortinet

CVE-2023-36641

MEDIUM · 6.5 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to after 7.2.5 or later.
See remediation →
71/100
Remediation priority · Elevated
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
A numeric truncation error in Fortinet FortiProxy version 7.2.0 through 7.2.4, FortiProxy version 7.0.0 through 7.0.10, FortiProxy 2.0 all versions, FortiProxy 1.2 all versions, FortiProxy 1.1, all versions, FortiProxy 1.0 all versions, FortiOS version 7.4.0, FortiOS version 7.2.0 through 7.2.5, FortiOS version 7.0.0 through 7.0.12, FortiOS 6.4 all versions, FortiOS 6.2 all versions, FortiOS 6.0 all versions allows attacker to denial of service via specifically 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 numeric truncation error in Fortinet FortiProxy and FortiOS allows remote attackers to cause denial of service via specifically crafted HTTP requests. The vulnerability affects multiple version ranges of both product lines and is triggered during HTTP request processing where numeric values are improperly handled, leading to a condition that can crash the service.

MitigationApply the vendor-supplied patches for FortiOS and FortiProxy as referenced in Fortinet advisory FG-IR-23-097. Until patches can be deployed, restrict access to management interfaces and implement rate limiting on HTTP services to reduce exploitability.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Fortinet product
    Run 'get system status' in the FortiOS/FortiProxy CLI or check the web UI dashboard to confirm whether the device is running FortiOS or FortiProxy
    Affected if The device runs FortiOS or FortiProxy (other Fortinet products are not affected)
  2. Determine the installed FortiOS version
    Run 'get system status' or 'get system version' in the CLI and note the firmware version number (for example, 7.0.5 or 6.4.12)
    Affected if The version falls within 6.0.0 to 6.0.17, 6.2.0 to 6.2.15, 6.4.0 to 6.4.14, 7.0.0 to 7.0.12, or 7.2.0 to 7.2.5
  3. Determine the installed FortiProxy version
    Run 'get system status' in the CLI and note the firmware version number shown for FortiProxy
    Affected if The version falls within 1.0.0 to 1.0.7, 1.1.0 to 1.1.6, 1.2.0 to 1.2.13, 2.0.0 to 2.0.13, 7.0.0 to 7.0.10, or 7.2.0 to 7.2.4
  4. Check if HTTP proxy service is exposed
    Run 'config system interface' then 'show' to list interface configurations; check for 'set http-proxy' enabled on external interfaces or review proxy policy settings with 'show firewall proxy-policy'
    Affected if HTTP/HTTPS proxy is enabled and accessible to untrusted networks (the vulnerability triggers during HTTP request processing)

The environment is affected if the device runs FortiOS or FortiProxy within the listed version ranges AND HTTP proxy services are exposed to network traffic that could contain specially crafted requests.

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.5
Interim mitigation

Apply the vendor-supplied patches for FortiOS and FortiProxy as referenced in Fortinet advisory FG-IR-23-097. Until patches can be deployed, restrict access to management interfaces and implement rate limiting on HTTP services to reduce exploitability.

Recommended fix High confidence

FortiOS: 7.2.6+, 7.0.13+, 6.4.15+, 6.2.16+, 6.0.18+, or 7.4.1+ | FortiProxy: 7.2.5+, 7.0.11+, or latest available version

  1. 1. Identify the currently installed FortiOS or FortiProxy version using: get system status (for FortiOS) or get system info (for FortiProxy)
  2. 2. For FortiOS 7.2.x: Upgrade to FortiOS 7.2.6 or later
  3. 3. For FortiOS 7.0.x: Upgrade to FortiOS 7.0.13 or later
  4. 4. For FortiOS 6.4.x: Upgrade to FortiOS 6.4.15 or later
  5. 5. For FortiOS 6.2.x: Upgrade to FortiOS 6.2.16 or later
  6. 6. For FortiOS 6.0.x: Upgrade to FortiOS 6.0.18 or later
  7. 7. For FortiProxy 7.2.x: Upgrade to FortiProxy 7.2.5 or later
  8. 8. For FortiProxy 7.0.x: Upgrade to FortiProxy 7.0.11 or later
Caveat Major version upgrades (e.g., 6.x to 7.x) may require configuration review and compatibility testing; review Fortinet upgrade guidelines before proceeding

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

Fix this in Fortiproxy Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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