dbcve.org
FortisoarApplication · Fortinet

CVE-2022-23443

HIGH · 7.5 CVSS v3.1 Published 2022-05-04
Fix available
A fix is available. Upgrade to after 7.0.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 access control in Fortinet FortiSOAR before 7.2.0 allows unauthenticated attackers to access gateway API data 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.0 contains an improper access control vulnerability where the gateway API endpoints do not properly enforce authentication. Attackers can send crafted HTTP GET requests to access sensitive gateway API data without any authentication credentials.

MitigationUpgrade FortiSOAR to version 7.2.0 or later to apply the vendor patch. If immediate patching is not possible, restrict network access to the FortiSOAR management interface to trusted IPs only as a compensating control.

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.2= 6.0.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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
    Locate the FortiSOAR application in your environment - this could be via service processes, installed packages, or access to the web management interface
    Affected if FortiSOAR is present in the environment
  2. Determine installed FortiSOAR version
    Access the FortiSOAR web interface and navigate to the About or Settings page to view the product version, or use the system's package management or configuration to retrieve the version number
    Affected if The installed version falls within 6.0.0, 6.4.0 through 6.4.4, or 7.0.0 through 7.0.2
  3. Test gateway API endpoint accessibility
    Send an unauthenticated HTTP GET request to the gateway API endpoint (typically /api/gateway/ or similar paths under the FortiSOAR API root) using a tool like curl or a browser, observe if the request returns sensitive data without providing any authentication tokens or credentials
    Affected if The gateway API responds with sensitive data or valid JSON responses without requiring authentication
  4. Verify authentication enforcement on API endpoints
    Compare responses from authenticated vs unauthenticated requests to the same gateway API endpoint - a vulnerable instance will return identical data for both requests
    Affected if Unauthenticated requests receive the same sensitive gateway API data as authenticated requests

You are affected if FortiSOAR versions 6.0.0, 6.4.0-6.4.4, or 7.0.0-7.0.2 are installed AND the gateway API endpoints are accessible without authentication credentials.

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 a release after 7.0.2
Interim mitigation

Upgrade FortiSOAR to version 7.2.0 or later to apply the vendor patch. If immediate patching is not possible, restrict network access to the FortiSOAR management interface to trusted IPs only as a compensating control.

Recommended fix High confidence

FortiSOAR 7.2.0 or later

  1. 1. Back up the current FortiSOAR configuration and database according to Fortinet backup procedures.
  2. 2. Download FortiSOAR version 7.2.0 or later from the Fortinet Customer Support Portal.
  3. 3. Review the FortiSOAR 7.2.0 release notes for any pre-upgrade requirements or migration steps.
  4. 4. Execute the upgrade following the standard FortiSOAR upgrade procedure (typically via the FortiSOAR UI or CLI).
  5. 5. Verify the upgrade completed successfully and confirm the version number.
  6. 6. Test that the gateway API now requires proper authentication.

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

Fix this in Fortisoar Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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