dbcve.org
FortiddosApplication · Fortinet

CVE-2022-27486

HIGH · 7.8 CVSS v3.1 Published 2024-08-13
Fix available
A fix is available. Upgrade to 5.6.2 / 6.4.2 or later.
See remediation →
80/100
Remediation priority · High
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
A improper neutralization of special elements used in an os command ('os command injection') in Fortinet FortiDDoS version 5.5.0 through 5.5.1, 5.4.2 through 5.4.0, 5.3.0 through 5.3.1, 5.2.0, 5.1.0, 5.0.0, 4.7.0, 4.6.0 and 4.5.0 and FortiDDoS-F version 6.3.0 through 6.3.1, 6.2.0 through 6.2.2, 6.1.0 through 6.1.4 allows an authenticated attacker to execute shell code as `root` via `execute` CLI commands.

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

This is an OS command injection vulnerability in Fortinet FortiDDoS and FortiDDoS-F appliances. An authenticated attacker can inject arbitrary shell commands through the execute CLI commands due to improper neutralization of special elements. The vulnerability allows execution of shell code with root privileges.

MitigationApply vendor-supplied patches by upgrading FortiDDoS to a fixed version (FortiDDoS 5.5.2 or later, 5.4.3 or later, 5.3.2 or later, or 6.1.5/6.2.3/6.3.2 or later). Restrict CLI access to trusted administrators only until the upgrade is completed.

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
FortiddosApplication
Affected:>= 4.5.0, < 5.6.2= 5.7.0
Fortiddos FApplication
Affected:all versions>= 6.1.0, < 6.4.2= 6.5.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 FortiDDoS product model
    Access the FortiDDoS CLI and run 'get system status' or check the web UI dashboard for the appliance model name (FortiDDoS vs FortiDDoS-F)
    Affected if The device is a FortiDDoS-F appliance (all versions affected) or FortiDDoS appliance (version 4.5.0 to 5.6.1, or 5.7.0)
  2. Determine installed firmware version
    Run 'get system status' in the FortiDDoS CLI or check System > Firmware in the web UI to obtain the exact version number
    Affected if The installed version falls within: FortiDDoS >= 4.5.0 and < 5.6.2, or = 5.7.0; FortiDDoS-F >= 6.1.0 and < 6.4.2, or = 6.5.0, or any version of FortiDDoS-F (all versions affected)
  3. Verify CLI access is exposed
    Check network configuration via 'show system interface' or examine firewall policies to determine if the CLI (port 22/SSH) is accessible from untrusted networks
    Affected if The CLI management interface is reachable from the network segment where the potential attacker resides, providing an attack vector for authenticated command injection
  4. Confirm administrative credentials exist
    Review user accounts via 'get system admin' in CLI or System > Administrators in the web UI to list accounts with CLI access privileges
    Affected if There are any administrative or operator accounts configured that could be compromised to provide authenticated access to the execute CLI commands
  5. Check execute command availability
    Log into the CLI with a low-privilege account and attempt to access execute commands (e.g., 'execute ?' or 'execute system ') to verify command execution is permitted
    Affected if The authenticated user can invoke execute commands, which is where the improper neutralization of special elements allows command injection

The environment is affected if the FortiDDoS device is a FortiDDoS-F model (any version) or a FortiDDoS model with version 4.5.0-5.6.1 or 5.7.0, and the CLI interface is accessible to an authenticated attacker who can execute arbitrary commands through the execute CLI functionality.

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.6.2 / 6.4.2 or later
Fixed in 5.6.26.4.2
Interim mitigation

Apply vendor-supplied patches by upgrading FortiDDoS to a fixed version (FortiDDoS 5.5.2 or later, 5.4.3 or later, 5.3.2 or later, or 6.1.5/6.2.3/6.3.2 or later). Restrict CLI access to trusted administrators only until the upgrade is completed.

Recommended fix High confidence

FortiDDoS: upgrade to >= 5.6.2 (excluding 5.7.0); FortiDDoS-F: upgrade to >= 6.4.2 (excluding 6.5.0)

  1. 1. Identify the currently installed FortiDDoS (or FortiDDoS-F) version via the GUI dashboard or CLI command: get system status
  2. 2. For FortiDDoS: If version is < 5.6.2 or version is 5.7.0, plan upgrade to version 5.6.2 or later (recommended: latest 5.x stable release)
  3. 3. For FortiDDoS-F: If version is < 6.4.2 or version is 6.5.0, plan upgrade to version 6.4.2 or later (recommended: latest 6.x stable release)
  4. 4. Backup current configuration via GUI: System > Maintenance > Backup & Restore, or CLI: execute backup config flash
  5. 5. Download the firmware image from Fortinet Customer Support portal (https://support.fortinet.com/) for the target version
  6. 6. Upload firmware via GUI: System > Firmware, or CLI: execute system firmware upgrade
  7. 7. After reboot, verify new version: get system status and confirm vulnerability is remediated
  8. 8. Restrict CLI execute command access to only necessary admin accounts via administrative user profiles
Caveat Review release notes for the target version for any configuration or behavioral changes before upgrading

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

Fix this in Fortiddos 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-2022-27486 — 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-2022-27486 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