dbcve.org
FortiadcApplication · Fortinet

CVE-2022-39947

HIGH · 8.8 CVSS v3.1 Published 2023-01-03
Fix available
A fix is available. Upgrade to after 6.2.3 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available

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.2, FortiADC version 6.2.0 through 6.2.3, FortiADC version version 6.1.0 through 6.1.6, FortiADC version 6.0.0 through 6.0.4, FortiADC version 5.4.0 through 5.4.5 may allow an attacker to execute unauthorized code or commands via specifically crafted HTTP requests.

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
How this class of weakness works · CWE-78

User input reaches a shell or system command without being fully separated from the command itself, so an attacker can append their own instructions. Because these run with the application's privileges, it often means full control of the host. The lasting fix is to avoid the shell entirely — call APIs directly and pass arguments as data, never as concatenated strings.

General guidance for the os command injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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.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= 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
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

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 a release after 6.2.3
Vendor patch fortiguard.com →
Recommended fix Moderate confidence

FortiADC 5.4.6+ / 6.0.5+ / 6.1.7+ / 6.2.4+ / 7.0.3+ (next available stable release in your branch)

  1. 1. Identify the currently installed FortiADC version via the web UI (Dashboard > Status) or CLI: get system status
  2. 2. Access FortiGuard security advisory FG-IR-22-061 at https://fortiguard.com/psirt/FG-IR-22-061 to obtain the official patch details
  3. 3. Based on your current major version branch, upgrade to the fixed release: for 5.4.x upgrade to 5.4.6 or later; for 6.0.x upgrade to 6.0.5 or later; for 6.1.x upgrade to 6.1.7 or later; for 6.2.x upgrade to 6.2.4 or later; for 7.0.x upgrade to 7.0.3 or later
  4. 4. Obtain the upgrade image from Fortinet's support portal (https://support.fortinet.com)
  5. 5. Upload the firmware via FortiADC web UI (System > Firmware) or CLI: execute firmware upload
  6. 6. After upgrade, verify the new version: get system status and confirm it is no longer in the affected range
  7. 7. Test that the HTTP request functionality continues to work correctly
Caveat Minor: Review release notes for any configuration or behavioral changes between your version and the upgrade target; test in staging if possible

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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