dbcve.org
FortimailApplication · Fortinet

CVE-2021-24008

MEDIUM · 5.3 CVSS v3.1 Published 2025-03-28
Fix available
A fix is available. Upgrade to 5.4.3 / 6.0.4 or later.
See remediation →
62/100
Remediation priority · Elevated
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
An exposure of sensitive system information to an unauthorized control sphere vulnerability [CWE-497] in FortiDDoS version 5.4.0, version 5.3.2 and below, version 5.2.0, version 5.1.0, version 5.0.0, version 4.7.0, version 4.6.0, version 4.5.0, version 4.4.2 and below, FortiDDoS-CM version 5.3.0, version 5.2.0, version 5.1.0, version 5.0.0, version 4.7.0, FortiVoice version 6.0.6 and below, FortiRecorder version 6.0.3 and below and FortiMail version 6.4.1 and below, version 6.2.4 and below, version 6.0.9 and below may allow a remote, unauthenticated attacker to obtain potentially sensitive software-version information by reading a JavaScript file.

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

An unauthenticated remote attacker can obtain sensitive software version information by reading JavaScript files served by the web interface of affected Fortinet products (FortiDDoS, FortiVoice, FortiRecorder, FortiMail). This information disclosure (CWE-497) could aid attackers in reconnaissance for more targeted exploits.

MitigationApply the vendor patches provided by Fortinet for the affected product versions. Until patches can be applied, consider restricting access to the web management interface to trusted networks only.

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
FortimailApplication
Affected:>= 6.0.0, < 6.0.10>= 6.2.0, < 6.2.5>= 6.4.0, < 6.4.2
FortiddosApplication
Affected:>= 4.4.0, < 5.4.3
FortivoiceApplication
Affected:>= 6.0.0, < 6.0.7
FortirecorderApplication
Affected:>= 6.0.0, < 6.0.4
Fortiddos CmApplication
Affected:= 4.7.0= 5.0.0= 5.1.0= 5.2.0= 5.3.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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 installed Fortinet product and version
    Log into the device via CLI and run the command: 'get system status' or 'fortimail -status' depending on the product. Alternatively, access the web login page and check any error messages or footer for version info.
    Affected if The displayed version matches any of the affected ranges: FortiMail 6.0.0-6.0.9, 6.2.0-6.2.4, or 6.4.0-6.4.1; FortiDDoS 4.4.0-5.4.2; FortiVoice 6.0.0-6.0.6; FortiRecorder 6.0.0-6.0.3; FortiDDoS CM 4.7.0, 5.0.0, 5.1.0, 5.2.0, or 5.3.0
  2. Confirm the web management interface is accessible
    Attempt to access the web interface URL (typically HTTPS on port 443) from a network location. Use a browser or curl command: 'curl -k https://<device-ip>/'
    Affected if The web interface responds and is reachable from your location, indicating the attack surface is exposed
  3. Verify JavaScript files are served by the web interface
    Access common JS file paths such as '/js/common.js' or '/static/js/' on the web interface using curl or browser. Example: 'curl -k https://<device-ip>/js/common.js'
    Affected if JavaScript files are returned and contain version information, confirming the information disclosure vector is present

You are affected if your Fortinet product is one of FortiMail, FortiDDoS, FortiVoice, or FortiRecorder, the web interface is accessible, and the installed version falls within the affected ranges listed.

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 5.4.3 / 6.0.4 / 6.0.7 or later
Fixed in 5.4.36.0.46.0.7
Interim mitigation

Apply the vendor patches provided by Fortinet for the affected product versions. Until patches can be applied, consider restricting access to the web management interface to trusted networks only.

Recommended fix High confidence

FortiMail: 6.0.10+/6.2.5+/6.4.2+ | FortiDDoS: 5.4.3+ | FortiVoice: 6.0.7+ | FortiRecorder: 6.0.4+ | FortiDDoS-CM: 5.3.1+

  1. 1. Identify the specific Forti product (FortiMail, FortiDDoS, FortiVoice, FortiRecorder, or FortiDDoS-CM) currently deployed in your environment.
  2. 2. Determine the exact current version of the deployed Forti product.
  3. 3. For FortiMail: upgrade to version 6.0.10, 6.2.5, or 6.4.2 or later depending on your current branch (6.0.x, 6.2.x, or 6.4.x).
  4. 4. For FortiDDoS: upgrade to version 5.4.3 or later.
  5. 5. For FortiVoice: upgrade to version 6.0.7 or later.
  6. 6. For FortiRecorder: upgrade to version 6.0.4 or later.
  7. 7. For FortiDDoS-CM: upgrade to version 5.3.1 or later.
  8. 8. After upgrade, verify the JavaScript file is no longer exposing software version information by attempting to access it without authentication.
Caveat Review FortiOS release notes for your product version for any configuration or behavioral changes between your current and target version

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

Fix this in Fortimail Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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