dbcve.org
FortisoarApplication · Fortinet

CVE-2022-30298

HIGH · 7.8 CVSS v3.1 Published 2022-09-06
Fix available
A fix is available. Upgrade to 7.0.3 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
An improper privilege management vulnerability [CWE-269] in Fortinet FortiSOAR before 7.2.1 allows a GUI user who has already found a way to modify system files (via another, unrelated and hypothetical exploit) to execute arbitrary Python commands as root.

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 improper privilege management vulnerability (CWE-269) in FortiSOAR before version 7.2.1. A GUI user who already possesses the ability to modify system files (achieved through a separate, unrelated exploit) can leverage this flaw to execute arbitrary Python commands with root privileges, achieving full system compromise.

MitigationUpgrade FortiSOAR to version 7.2.1 or later to remediate this vulnerability.

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.0, <= 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
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. Confirm FortiSOAR is installed
    Access the FortiSOAR login page via web browser at your FortiSOAR hostname/IP, or check for FortiSOAR processes running on the server using commands like 'ps aux | grep -i fortisoar' or 'systemctl list-units | grep fortisoar'
    Affected if FortiSOAR is not installed or not accessible - if not FortiSOAR, this CVE does not apply
  2. Identify the installed FortiSOAR version
    Log into FortiSOAR GUI, click the user menu (top-right), select Help > About to view the version number; alternatively, check the file '/opt/fsr-ui/.build_info' or run 'docker ps' to identify container versions if CLI access is available
    Affected if Version falls within >= 6.4.0 to <= 6.4.4, OR >= 7.0.0 to < 7.0.3, OR equals 7.2.0 exactly - if so, the version is vulnerable
  3. Verify GUI access exists
    Confirm you have valid FortiSOAR GUI credentials and can log into the web interface; check if GUI is accessible over HTTPS/HTTP on port 8000 or configured port
    Affected if GUI access is available - the vulnerability requires a GUI user to exploit the flaw, so lack of GUI access means the attack vector does not apply
  4. Check for users with system file modification capability
    In FortiSOAR GUI, navigate to Administration > Users > Roles and review which roles have permissions to modify system files or execute scripts; or use CLI to check '/opt/fsr-ui/configs/user_roles.json' if accessible
    Affected if Any GUI user account possesses permissions to modify system files or execute scripts - this is the prerequisite condition required for exploitation; without this capability, the privilege escalation path does not apply

You are affected if FortiSOAR is running a vulnerable version (6.4.0-6.4.4, 7.0.0-7.0.3, or 7.2.0) AND a GUI user account exists with permissions to modify system files, as the vulnerability allows such a user to escalate to root-level code execution.

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 remediate this vulnerability.

Recommended fix High confidence

FortiSOAR 7.2.1 or later

  1. 1. Back up your current FortiSOAR configuration and data.
  2. 2. Download FortiSOAR version 7.2.1 or later from the Fortinet support portal.
  3. 3. Review the FortiSOAR upgrade guide for your current version.
  4. 4. Execute the upgrade following Fortinet's standard upgrade procedure.
  5. 5. Verify the upgrade was successful by logging into the FortiSOAR console.
  6. 6. Confirm the vulnerability is resolved by checking the FortiSOAR version display.
Caveat Review Fortinet release notes for any configuration or compatibility changes between your current version and 7.2.1

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

Fix this in Fortisoar Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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