dbcve.org
FortimanagerApplication · Fortinet

CVE-2021-24006

HIGH · 8.8 CVSS v3.1 Published 2021-09-06
Fix available
A fix is available. Upgrade to 6.4.4 or later.
See remediation →
94/100
Remediation priority · Urgent
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
An improper access control vulnerability in FortiManager versions 6.4.0 to 6.4.3 may allow an authenticated attacker with a restricted user profile to access the SD-WAN Orchestrator panel via directly visiting its 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

FortiManager versions 6.4.0 through 6.4.3 contain an improper access control vulnerability where authenticated users with restricted user profiles can access the SD-WAN Orchestrator panel by directly visiting its URL, bypassing intended role-based access controls.

MitigationUpgrade FortiManager to version 6.4.4 or later to obtain the patch. Additionally, review and restrict user profiles to ensure only authorized personnel have access to sensitive features like SD-WAN Orchestrator.

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
FortimanagerApplication
Affected:>= 6.4.0, < 6.4.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify FortiManager version
    Run the command 'get system status' in FortiManager CLI or check the Dashboard > System Information widget in the GUI to view the current firmware version.
    Affected if The installed version is 6.4.0, 6.4.1, 6.4.2, or 6.4.3.
  2. Confirm vulnerable version range
    Compare the identified version against the affected range: versions 6.4.0 through 6.4.3 are vulnerable. Versions below 6.4.0 and 6.4.4 or higher are not affected.
    Affected if The version falls within 6.4.0 to 6.4.3 inclusive.
  3. Review user profiles with restricted access
    Navigate to System > Admin > User & Device > User Definition or run 'show system accprofile' in CLI to list all defined user profiles and their privilege levels.
    Affected if User profiles exist with limited or restricted privileges that should not have SD-WAN Orchestrator access.
  4. Verify SD-WAN Orchestrator access controls
    Navigate to SD-WAN > SD-WAN Orchestrator or attempt to access the URL pattern '/ng/sdwan/' directly while logged in as a restricted user account. Check if restricted users can reach the Orchestrator interface.
    Affected if Restricted users can access the SD-WAN Orchestrator panel by directly navigating to its URL, indicating the access control bypass exists.

You are affected if your FortiManager version is 6.4.0 through 6.4.3 and restricted user accounts can access the SD-WAN Orchestrator panel without proper authorization.

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.4 or later
Fixed in 6.4.4
Interim mitigation

Upgrade FortiManager to version 6.4.4 or later to obtain the patch. Additionally, review and restrict user profiles to ensure only authorized personnel have access to sensitive features like SD-WAN Orchestrator.

Recommended fix High confidence

6.4.4

  1. Backup FortiManager configuration and data before initiating upgrade
  2. Review FortiManager 6.4.4 release notes for any specific upgrade requirements or migration considerations
  3. Perform upgrade from affected versions (6.4.0-6.4.3) to version 6.4.4 or later
  4. After upgrade, verify that restricted user profiles correctly deny access to the SD-WAN Orchestrator panel
Caveat Review release notes for any configuration changes or behavioral differences in FortiManager 6.4.4

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

Fix this in Fortimanager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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