FortiproxyApplication · Fortinet
CVE-2023-22640
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 · uneditedA out-of-bounds write in Fortinet FortiOS version 7.2.0 through 7.2.3, FortiOS version 7.0.0 through 7.0.10, FortiOS version 6.4.0 through 6.4.11, FortiOS version 6.2.0 through 6.2.13, FortiOS all versions 6.0, FortiProxy version 7.2.0 through 7.2.1, FortiProxy version 7.0.0 through 7.0.7, FortiProxy all versions 2.0, FortiProxy all versions 1.2, FortiProxy all versions 1.1, FortiProxy all versions 1.0 allows an authenticated attacker to execute unauthorized code or commands via specifically crafted 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 confidenceAn out-of-bounds write vulnerability in FortiOS and FortiProxy allows authenticated attackers to execute unauthorized code or commands via specifically crafted HTTP requests. The vulnerability exists due to improper bounds checking when processing certain requests in the affected versions.
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
= 1.0.0= 1.1.0= 1.2.0= 2.0.0
FortiosOperating system
>= 6.0.0, <= 6.0.16>= 6.2.0, < 6.2.14>= 6.4.0, < 6.4.12>= 7.0.0, < 7.0.11>= 7.2.0, < 7.2.4CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Fortinet product and versionLog into the FortiOS or FortiProxy CLI and run the command: get system status. This displays the product name, version, and build number.Affected if The version displayed falls within the affected ranges: FortiProxy 1.0.0-2.0.0, FortiOS 6.0.0-6.0.16, 6.2.0-6.2.13, 6.4.0-6.4.11, 7.0.0-7.0.10, or 7.2.0-7.2.3.
-
Confirm the HTTP management interface is enabledIn the CLI, run: get system interface. Look for an interface with management access enabled (http or https listed in the access field).Affected if HTTP or HTTPS management access is enabled on any interface, making the web UI reachable over the network.
-
Check if admin access is exposed to untrusted networksRun: show system admin. Review the trusted host settings for each admin account. Also run: show system interface to inspect which interfaces have management access.Affected if Administrative accounts either have no trusted host restrictions or the management interface is bound to an interface accessible from untrusted networks.
-
Review recent authentication logs for anomalous HTTP requestsRun: execute log filter category event. Then: execute log display. Look for unusual HTTP requests or authentication events around the time of potential exploitation.Affected if Unexpected authentication events, especially from authenticated users making unusual HTTP requests, are present in the logs.
You are affected if your FortiOS or FortiProxy version falls within the listed affected version ranges and the HTTP management interface is accessible from the network.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.2.146.4.127.0.11
Upgrade to Fortinet patched versions (FortiOS 7.2.4+, 7.0.11+, 6.4.12+, 6.2.14+, 6.0.16+ and FortiProxy 7.2.2+, 7.0.8+) or apply available security patches. If patching is delayed, restrict administrative interface access to trusted IP addresses only and monitor for Indicators of Compromise.
FortiOS: 6.0.17+, 6.2.14+, 6.4.12+, 7.0.11+, 7.2.4+ | FortiProxy: 1.0.1+, 1.1.1+, 1.2.1+, 2.0.1+, 7.0.8+, 7.2.2+
- 1. Identify the currently installed FortiOS or FortiProxy version via the web UI (System > Firmware) or CLI: `get system status`
- 2. For FortiOS 6.0.x: Upgrade to version 6.0.17 or later
- 3. For FortiOS 6.2.x: Upgrade to version 6.2.14 or later
- 4. For FortiOS 6.4.x: Upgrade to version 6.4.12 or later
- 5. For FortiOS 7.0.x: Upgrade to version 7.0.11 or later
- 6. For FortiOS 7.2.x: Upgrade to version 7.2.4 or later (7.2.0-7.2.3 are affected per official description)
- 7. For FortiProxy 1.0.x: Upgrade to version 1.0.1 or later
- 8. For FortiProxy 1.1.x: Upgrade to version 1.1.1 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortiproxy
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2023-22640 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-22640 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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