dbcve.org
FortiadcApplication · Fortinet

CVE-2022-27482

HIGH · 7.8 CVSS v3.1 Published 2023-02-16
Fix available
A fix is available. Upgrade to 6.2.4 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 FortiADC version 7.0.0 through 7.0.1, 6.2.0 through 6.2.2, 6.1.0 through 6.1.6, 6.0.x, 5.x.x allows attacker to execute arbitrary shell code as `root` via 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

OS command injection vulnerability in FortiADC CLI allows attackers to inject arbitrary shell commands through improperly sanitized input in CLI commands, resulting in root-level code execution.

MitigationUpdate to patched FortiADC version beyond 7.0.1/6.2.2/6.1.6; implement proper input validation and escaping for all CLI command parameters to prevent shell metacharacter injection.

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
FortiadcApplication
Affected:>= 5.0.0, <= 5.0.4>= 5.1.0, <= 5.1.7>= 5.2.0, <= 5.2.8>= 5.3.0, <= 5.3.7>= 5.4.0, <= 5.4.5>= 6.0.0, <= 6.0.4>= 6.1.0, <= 6.1.6>= 6.2.0, < 6.2.4= 7.0.0= 7.0.1

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 the FortiADC device
    Run 'get system status' or 'diagnose sys version' command in the FortiADC CLI console to confirm the device model and confirm it is a FortiADC appliance
    Affected if The device model is not FortiADC, then this CVE does not apply
  2. Determine the FortiADC firmware version
    Execute 'get system status' in the FortiADC CLI or check the web UI dashboard for the firmware version number
    Affected if The version displayed is within any of these ranges: 5.0.0-5.0.4, 5.1.0-5.1.7, 5.2.0-5.2.8, 5.3.0-5.3.7, 5.4.0-5.4.5, 6.0.0-6.0.4, 6.1.0-6.1.6, 6.2.0-6.2.3, or exactly 7.0.0-7.0.1
  3. Verify CLI access exposure
    Check network configuration via 'get system interface' and review which management interfaces (HTTP/HTTPS/SSH) are enabled and accessible. Confirm that the CLI is reachable over network interfaces rather than only local console
    Affected if SSH or console CLI access is enabled and reachable from network segments where untrusted users could input commands
  4. Review CLI command logging
    Examine FortiADC logs for any unusual or unexpected CLI commands executed, particularly those containing shell metacharacters such as ; | & $ ` or command substitutions. Check 'execute log' and 'diagnose log' outputs
    Affected if Logs show CLI commands with shell metacharacters or commands not initiated by legitimate administrators

Your FortiADC is affected if it runs any firmware version within 5.0.0-5.0.4, 5.1.0-5.1.7, 5.2.0-5.2.8, 5.3.0-5.3.7, 5.4.0-5.4.5, 6.0.0-6.0.4, 6.1.0-6.1.6, 6.2.0-6.2.3, 7.0.0, or 7.0.1 and has network-accessible CLI interfaces.

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.2.4 or later
Fixed in 6.2.4
Interim mitigation

Update to patched FortiADC version beyond 7.0.1/6.2.2/6.1.6; implement proper input validation and escaping for all CLI command parameters to prevent shell metacharacter injection.

Recommended fix High confidence

FortiADC 5.3.8 or later (recommended: latest 5.3.x stable release)

  1. 1. Identify the current FortiADC firmware version by running `get system status` or `fnsysctl cat /etc/version` in CLI
  2. 2. Download the patched firmware version 5.3.8 or later from Fortinet's support portal (https://support.fortinet.com)
  3. 3. Backup the current FortiADC configuration using `execute backup config` command
  4. 4. Upload the new firmware via Web UI (System > Firmware > Upload) or CLI: `execute upload firmware <tftp|ftp> <filename>`
  5. 5. Reboot the device to apply the new firmware: `execute reboot`
  6. 6. After reboot, verify the new version is installed: `get system status`
  7. 7. Verify the configuration integrity: `execute backup config` and compare with backup from step 3
Caveat Review FortiADC 5.3.8 release notes for any configuration or feature changes before upgrading; test in staging environment first

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

Fix this in Fortiadc Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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