dbcve.org
FortisoarApplication · Fortinet

CVE-2022-29061

HIGH · 7.2 CVSS v3.1 Published 2022-09-09
Fix available
A fix is available. Upgrade to 7.0.3 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
An improper neutralization of special elements used in an OS command ('OS Command Injection') vulnerability [CWE-78] in Fortinet FortiSOAR before 7.2.1 allows an authenticated attacker to execute unauthorized code or commands via crafted HTTP GET 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 · high confidence

FortiSOAR before version 7.2.1 contains an OS command injection vulnerability (CWE-78) where authenticated attackers can execute arbitrary operating system commands via specially crafted HTTP GET requests. The vulnerability requires valid authentication but allows complete compromise of the underlying system once exploited.

MitigationUpgrade FortiSOAR to version 7.2.1 or later to patch the command injection vulnerability. As a SOAR platform handles critical security operations, ensure the upgrade is thoroughly tested in a non-production environment before deployment.

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
FortisoarApplication
Affected:>= 6.4.1, <= 6.4.4>= 7.0.0, < 7.0.3= 7.2.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
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 FortiSOAR installation and version
    Log into the FortiSOAR web UI and navigate to the Settings or About page to view the product version. Alternatively, access the server via SSH and run: dpkg -l | grep fortisoar or check /opt/fsr.VERSION if the file exists.
    Affected if The installed version matches any of these ranges: 6.4.1 through 6.4.4, 7.0.0 through 7.0.2, or exactly 7.2.0
  2. Verify web interface is accessible
    Confirm that the FortiSOAR web interface (HTTPS on port 443 or custom port) is reachable from a network perspective. Check firewall rules and service status with: systemctl status nginx or check which ports are listening with netstat -tlnp.
    Affected if The web interface is exposed and the version falls within the affected ranges listed above
  3. Confirm authentication is enabled
    Verify that FortiSOAR requires valid credentials for access. Check the authentication configuration in the Admin settings or verify that login is required by attempting an unauthenticated request which should be rejected.
    Affected if Valid authentication is required (as expected) and the version is affected - the vulnerability allows command execution AFTER authentication

If FortiSOAR version is 6.4.1-6.4.4, 7.0.0-7.0.2, or exactly 7.2.0 AND the web interface is accessible, the environment is affected by this command injection vulnerability.

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 7.0.3 or later
Fixed in 7.0.3
Interim mitigation

Upgrade FortiSOAR to version 7.2.1 or later to patch the command injection vulnerability. As a SOAR platform handles critical security operations, ensure the upgrade is thoroughly tested in a non-production environment before deployment.

Recommended fix High confidence

FortiSOAR 7.2.1 or later (for affected 6.4.x and 7.0.x versions, upgrade to 7.2.1 or later)

  1. 1. Identify the current FortiSOAR version by navigating to the Adminstration > System Settings > About page in the FortiSOAR console
  2. 2. If running version 6.4.1 through 6.4.4, or 7.0.0 through 7.0.2, or exactly 7.2.0, plan for an upgrade to version 7.2.1 or later
  3. 3. Before upgrading, create a complete backup of the FortiSOAR database and configuration
  4. 4. Download FortiSOAR version 7.2.1 or the latest stable version from the Fortinet Customer Support Portal
  5. 5. Review the FortiSOAR upgrade guide for your current version to ensure all prerequisites are met
  6. 6. Schedule a maintenance window as upgrades may require downtime
  7. 7. Execute the upgrade following Fortinet's official upgrade procedure
  8. 8. After upgrade completion, verify the new version is 7.2.1 or later in Administration > System Settings > About
Caveat Review FortiSOAR release notes for 7.2.1 for any configuration or feature changes that may require adjustment

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

Fix this in Fortisoar Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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