Safeguard
Vulnerability Analysis•

CVE-2022-27486: Medium OS Command Injection in FortiDDoS CLI

CVE-2022-27486 is OS command injection in the FortiDDoS CLI, scored 6.6. Upgrade FortiDDoS to 5.7.1 or FortiDDoS-F to 6.5.1 or later, or migrate.

Safeguard Security Team
3 min read

CVE-2022-27486 is a medium severity OS command injection in the CLI of Fortinet FortiDDoS and FortiDDoS-F, scored 6.6. An authenticated attacker can run shell code as root through execute commands. Fortinet's fix is 5.7.1 or later on 5.7, and 6.5.1 or later on FortiDDoS-F 6.5.

What's affected

Fortinet's advisory FG-IR-22-047, published 13 August 2024, rates the issue Medium and lists the CLI as the component. It was discovered internally by Fortinet's product security team. It gives this guidance by branch:

  • FortiDDoS 5.7.0: upgrade to 5.7.1 or above.
  • FortiDDoS 5.6.0 through 5.6.1: upgrade to 5.6.2 or above.
  • FortiDDoS 5.5, 5.4, 5.3, 5.2, 5.1, 5.0, 4.7, 4.6 and 4.5: all versions affected, migrate to a fixed release.
  • FortiDDoS-F 6.5.0: upgrade to 6.5.1 or above.
  • FortiDDoS-F 6.4.0 through 6.4.1: upgrade to 6.4.2 or above.
  • FortiDDoS-F 6.3, 6.2 and 6.1: all versions affected, migrate to a fixed release.

The NVD record lists a narrower set of versions, for example FortiDDoS-F 6.1.0 through 6.1.4, and does not mention the 5.6, 5.7, 6.4 or 6.5 branches. The advisory's table is more complete, so use that.

The NVD score is 6.6 with a local vector and low privileges, and the record's kev flag is false.

Weakness class per the record: CWE-78.

How to check if you're exposed

Log in to the appliance and check the firmware version in the web interface dashboard or with the CLI:

get system status

Compare the version line with the branch list above. Appliances on 5.5 or older, or on FortiDDoS-F 6.3 or older, are affected at every release and need a migration to a fixed branch, not a patch within the branch.

Also list who has CLI access. The attack requires an authenticated session and the use of execute commands, so a short list of administrators lowers exposure.

What to do now

  1. Record the FortiDDoS and FortiDDoS-F firmware versions you run.
  2. Upgrade to 5.7.1, 5.6.2, 6.5.1 or 6.4.2 or later depending on your branch, or plan a migration if you are on an older branch.
  3. Reduce CLI and administrative access to named administrators and trusted management networks.
  4. Check the vendor notes for upgrade paths between branches before scheduling the change.

Why it matters

This is OS command injection (CWE-78): input to a CLI command ends up interpreted by the underlying shell, and the resulting commands run as root. The CLI is meant for administrators, so the flaw mostly matters where administrator accounts are shared, over broad, or compromised.

Even so, a device that sits in front of your services to absorb attacks is an attractive place to hold a root level foothold. A compromised DDoS appliance can see and alter traffic that you assumed it protected.

The long tail of unsupported branches in the advisory is a reminder that appliance upgrades are often skipped for years. The fix is a migration rather than a patch for much of the older fleet.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Is there a patch for FortiDDoS 5.5 or older?

The advisory says all versions of those branches are affected and tells owners to migrate to a fixed release rather than patch within the branch.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.