dbcve.org
FortiproxyApplication · Fortinet

CVE-2023-22641

MEDIUM · 5.4 CVSS v3.1 Published 2023-04-11
Fix available
A fix is available. Upgrade to 6.4.13 / 7.0.9 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 url redirection to untrusted site ('open redirect') in Fortinet FortiOS version 7.2.0 through 7.2.3, FortiOS version 7.0.0 through 7.0.9, FortiOS versions 6.4.0 through 6.4.12, FortiOS all versions 6.2, FortiOS all versions 6.0, FortiProxy version 7.2.0 through 7.2.2, FortiProxy version 7.0.0 through 7.0.8, 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 specially 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 · moderate confidence

FortiOS and FortiProxy contain an open redirect vulnerability where an authenticated attacker can manipulate URL parameters to redirect users to malicious sites. Despite the title indicating URL redirection, the description also references potential unauthorized code/command execution via crafted requests, suggesting possible additional impact in certain contexts.

MitigationApply Fortinet patches for the specified versions: FortiOS 7.2.4+, 7.0.10+, 6.4.13+, or upgrade beyond affected versions; FortiProxy 7.2.3+, 7.0.9+, or upgrade beyond affected versions. Implement URL validation for redirect parameters.

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, <= 2.0.12>= 7.0.0, < 7.0.9>= 7.2.0, < 7.2.3
FortiosOperating system
Affected:>= 6.0.0, < 6.4.13>= 7.0.0, < 7.0.11>= 7.2.0, < 7.2.4

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 product and version
    Run the CLI command 'get system status' on the FortiOS/FortiProxy device to retrieve the product name and firmware version.
    Affected if The device runs FortiOS version 6.0.0 to <6.4.13, 7.0.0 to <7.0.11, or 7.2.0 to <7.2.4; OR FortiProxy version 1.0.0 to 2.0.12, 7.0.0 to <7.0.9, or 7.2.0 to <7.2.3.
  2. Confirm web interface access is enabled
    Check if the web UI (HTTPS administrative interface) or SSL-VPN is enabled by running 'get system interface' and reviewing the 'set http' or 'set https' and 'set sslvpn' settings in the configuration.
    Affected if The web administrative interface or SSL-VPN service is accessible to authenticated users, as the vulnerability requires an authenticated session to manipulate redirect parameters.
  3. Review logs for suspicious redirect activity
    Inspect the SSL-VPN and web UI logs (via 'execute log filter' and 'execute log display') for entries containing unusual URL parameters that may indicate redirect manipulation attempts.
    Affected if Logs show unexpected redirect URL parameters in user requests or patterns where 'redirect' or 'url' parameters point to external domains.

The environment is affected if the device runs a vulnerable FortiOS or FortiProxy version within the specified ranges AND the web interface or SSL-VPN is accessible to authenticated users who could trigger the redirect manipulation.

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 6.4.13 / 7.0.9 / 7.0.11 or later
Fixed in 6.4.137.0.97.0.11
Interim mitigation

Apply Fortinet patches for the specified versions: FortiOS 7.2.4+, 7.0.10+, 6.4.13+, or upgrade beyond affected versions; FortiProxy 7.2.3+, 7.0.9+, or upgrade beyond affected versions. Implement URL validation for redirect parameters.

Recommended fix High confidence

FortiOS: 6.4.13+, 7.0.11+, or 7.2.4+ | FortiProxy: 7.0.9+ or 7.2.3+ (older 1.x-2.0.x should migrate to supported versions)

  1. 1. Identify the current FortiOS or FortiProxy version installed on the device using the CLI command: get system status
  2. 2. Based on the current version, determine the appropriate upgrade path to a fixed release:
  3. - For FortiOS 6.x: Upgrade to version 6.4.13 or later, or 7.0.11 or later, or 7.2.4 or later
  4. - For FortiOS 7.0.x: Upgrade to version 7.0.11 or later
  5. - For FortiOS 7.2.x: Upgrade to version 7.2.4 or later
  6. - For FortiProxy 1.x-2.0.x: Upgrade to version 2.0.13 or later (if available), or migrate to supported 7.x versions
  7. - For FortiProxy 7.0.x: Upgrade to version 7.0.9 or later
  8. - For FortiProxy 7.2.x: Upgrade to version 7.2.3 or later
Caveat Review Fortinet release notes for each major version upgrade for potential configuration or feature changes; always test in a non-production environment first

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

Fix this in Fortiproxy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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