dbcve.org
FortiauthenticatorApplication · Fortinet

CVE-2024-23664

MEDIUM · 6.1 CVSS v3.1 Published 2024-06-03
Fix available
A fix is available. Upgrade to 6.5.4 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 FortiAuthenticator version 6.6.0, version 6.5.3 and below, version 6.4.9 and below may allow an attacker to to redirect users to an arbitrary website via a crafted URL.

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

FortiAuthenticator versions 6.6.0, 6.5.3 and below, and 6.4.9 and below contain an open redirect vulnerability where the application uses user-supplied input to determine the redirect destination without proper validation, allowing attackers to craft malicious URLs that appear to originate from the legitimate FortiAuthenticator site.

MitigationApply the vendor-supplied patch or firmware update from Fortinet to remediate this vulnerability; validate that redirect parameters are properly validated against an allowlist of trusted domains.

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
FortiauthenticatorApplication
Affected:>= 6.4.0, < 6.5.4= 6.6.0

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Check FortiAuthenticator firmware version via CLI
    Log into the FortiAuthenticator CLI and run the command: `get system status` or `execute getsysinfo`. Locate the Version field in the output.
    Affected if The displayed version falls within these ranges: 6.4.0 through 6.4.9, any 6.5.x version up to and including 6.5.3, or exactly version 6.6.0.
  2. Check FortiAuthenticator firmware version via GUI
    Log into the FortiAuthenticator web GUI. Navigate to System > Settings or click the user menu to access About/Dashboard. Locate the firmware version displayed.
    Affected if The displayed version matches the vulnerable ranges listed above.
  3. Verify specific vulnerable version against allowlist
    If you have confirmed a version number, manually compare it to the affected ranges: 6.4.0 <= version < 6.5.4, or version == 6.6.0.
    Affected if Your installed version is 6.4.0 through 6.4.9, 6.5.0 through 6.5.3, or exactly 6.6.0.

You are affected if your FortiAuthenticator version is 6.4.0 through 6.4.9, 6.5.0 through 6.5.3, or specifically version 6.6.0.

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.5.4 or later
Fixed in 6.5.4
Interim mitigation

Apply the vendor-supplied patch or firmware update from Fortinet to remediate this vulnerability; validate that redirect parameters are properly validated against an allowlist of trusted domains.

Recommended fix High confidence

FortiAuthenticator 6.5.4 or later (for 6.4.x/6.5.x installs); FortiAuthenticator 6.6.1 or later (for 6.6.0 installs)

  1. 1. Identify the current FortiAuthenticator version via the Web UI (Dashboard > System Information) or CLI: execute get system status
  2. 2. If running version 6.4.x or 6.5.x (6.5.0-6.5.3), upgrade to version 6.5.4 or later
  3. 3. If running version 6.6.0, upgrade to version 6.6.1 or later
  4. 4. Download the firmware upgrade from https://www.fortinet.com/support/firmware
  5. 5. Upload and install the firmware via FortiAuthenticator Web UI: System > Firmware > Upload or via CLI: execute system firmware upgrade
  6. 6. After upgrade, verify the new version is installed and test that the redirect functionality works correctly
Caveat Standard firmware upgrade - review release notes for any configuration migration requirements

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

Fix this in Fortiauthenticator Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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