dbcve.org
FortiadcApplication · Fortinet

CVE-2022-43948

HIGH · 7.8 CVSS v3.1 Published 2023-04-11
Fix available
A fix is available. Upgrade to 6.2.6 / 7.0.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 FortiWeb version 7.0.0 through 7.0.3, FortiADC version 7.1.0 through 7.1.1, FortiADC version 7.0.0 through 7.0.3, FortiADC 6.2 all versions, FortiADC 6.1 all versions, FortiADC 6.0 all versions, FortiADC 5.4 all versions, FortiADC 5.3 all versions, FortiADC 5.2 all versions, FortiADC 5.1 all versions allows attacker to execute unauthorized code or commands via specifically crafted arguments to existing 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 (CWE-78) in FortiWeb and FortiADC appliances. Attackers can execute unauthorized code or commands via specifically crafted arguments to existing commands due to improper neutralization of special elements in OS command contexts. The vulnerability affects a wide range of FortiADC versions (5.1 through 7.1.1) and FortiWeb 7.0.0 through 7.0.3.

MitigationApply the vendor-supplied patches by upgrading FortiWeb to version 7.0.4 or later and FortiADC to the latest available fixed version. Until patches are applied, restrict administrative interface access to trusted networks only.

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.1.0, < 6.2.6>= 7.0.0, < 7.0.4>= 7.1.0, < 7.1.2
FortiwebApplication
Affected:>= 7.0.0, < 7.0.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
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 installed Fortinet product
    Access the appliance CLI or admin GUI and run the command to display the system hostname and model information, or check the dashboard for the product name
    Affected if The product is FortiWeb or FortiADC
  2. Determine the firmware version
    Run the command to display the current FortiOS/FortiWeb firmware version, typically via 'get system status' or 'fnsysctl cat /etc/version' in CLI
    Affected if The version falls within FortiADC 5.1.0 to 6.2.5, 7.0.0 to 7.0.3, or 7.1.0 to 7.1.1; OR FortiWeb 7.0.0 to 7.0.3
  3. Check admin interface network exposure
    Review the network configuration for the administrative interface (port1 or mgmt interface) to determine if it is bound to a wide-scope IP address or is accessible from untrusted networks
    Affected if The admin interface is listening on 0.0.0.0 or an IP accessible from the internet or untrusted networks
  4. Verify admin access restrictions
    Review the administrative access settings in the web UI under System > Network > Interface, or use CLI to list admin user and trusted host configurations
    Affected if No trusted host restrictions are configured for admin accounts, or the admin service is open to any source IP

The environment is affected if the device runs FortiADC version 5.1.0-6.2.5, 7.0.0-7.0.3, or 7.1.0-7.1.1, or FortiWeb version 7.0.0-7.0.3, AND the administrative interface is accessible from untrusted networks.

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.6 / 7.0.4 / 7.1.2 or later
Fixed in 6.2.67.0.47.1.2
Interim mitigation

Apply the vendor-supplied patches by upgrading FortiWeb to version 7.0.4 or later and FortiADC to the latest available fixed version. Until patches are applied, restrict administrative interface access to trusted networks only.

Recommended fix High confidence

FortiADC: upgrade to 6.2.6, 7.0.4, or 7.1.2 or later branches; FortiWeb: upgrade to 7.0.4 or later

  1. 1. Identify the currently installed FortiADC or FortiWeb version using the CLI command 'get system status' or through the web UI under Dashboard > Status
  2. 2. For FortiADC 5.1.x through 5.4.x: Upgrade to FortiADC 6.2.6 or later (6.2.x is the recommended stable branch)
  3. 3. For FortiADC 6.0.x through 6.2.x: Upgrade to FortiADC 6.2.6 or later
  4. 4. For FortiADC 7.0.x: Upgrade to FortiADC 7.0.4 or later (7.0.4 is the minimum fixed version)
  5. 5. For FortiADC 7.1.x: Upgrade to FortiADC 7.1.2 or later
  6. 6. For FortiWeb 7.0.x: Upgrade to FortiWeb 7.0.4 or later
  7. 7. Download the appropriate firmware from Fortinet's support portal (https://support.fortinet.com/)
  8. 8. Upload the firmware through the web UI (System > Firmware) or CLI using 'execute firmware upload' command
Caveat Major version upgrades (e.g., 5.x to 6.x, 6.x to 7.x) may require configuration review and testing in a staging environment due to potential feature/command changes

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

Fix this in Fortiadc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.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-43948 — 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-43948 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