dbcve.org
FortisoarApplication · Fortinet

CVE-2022-42473

MEDIUM · 5.5 CVSS v3.1 Published 2022-11-02
Fix available
A fix is available. Upgrade to after 7.0.3 or later.
See remediation →
57/100
Remediation priority · Elevated
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 missing authentication for a critical function vulnerability in Fortinet FortiSOAR 6.4.0 - 6.4.4 and 7.0.0 - 7.0.3 and 7.2.0 allows an attacker to disclose information via logging into the database using a privileged account without a password.

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

Fortinet FortiSOAR versions 6.4.0-6.4.4, 7.0.0-7.0.3, and 7.2.0 contain a missing authentication vulnerability allowing unauthenticated attackers to access the database using a privileged account without a password, resulting in information disclosure.

MitigationUpgrade FortiSOAR to version 6.4.5, 7.0.4, 7.2.1, or later per Fortinet advisory, and verify the privileged database account requires proper authentication.

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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 installed FortiSOAR version
    Access the FortiSOAR admin interface and navigate to the System Settings or About page to view the current version, or use the CLI command 'fwconsole --version' if available
    Affected if The installed version is 6.4.0 through 6.4.4, 7.0.0 through 7.0.3, or exactly 7.2.0
  2. Locate the database configuration file
    Examine the FortiSOAR configuration directory for database connection settings, typically found in configuration files under /opt/cs-dashboard/ or similar installation paths
    Affected if The configuration reveals a privileged database account (often named 'bol' or similar system account) with no password or blank password field
  3. Verify database authentication for privileged accounts
    Inspect the database user configuration or connection strings to confirm whether the privileged account requires a password for authentication
    Affected if The privileged database account is configured with no password or authentication is not enforced
  4. Check database access controls
    Review network or application-level access controls that restrict database connections to authenticated sessions only
    Affected if Unauthenticated access to the database layer is permitted or the application bypasses authentication for database operations

You are affected if FortiSOAR version is 6.4.0-6.4.4, 7.0.0-7.0.3, or 7.2.0 AND the privileged database account has no password configured or authentication is missing.

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.3
Interim mitigation

Upgrade FortiSOAR to version 6.4.5, 7.0.4, 7.2.1, or later per Fortinet advisory, and verify the privileged database account requires proper authentication.

Recommended fix Moderate confidence

FortiSOAR 7.2.1 or latest stable 7.x release

  1. Identify your current FortiSOAR version (6.4.x, 7.0.x, or 7.2.0)
  2. Schedule a maintenance window and backup the FortiSOAR database
  3. Upgrade to FortiSOAR 7.2.1 or later (recommended)
  4. Alternatively, upgrade to 6.4.5 or later if staying on 6.x branch
  5. Alternatively, upgrade to 7.0.4 or later if staying on 7.0.x branch
  6. After upgrade, verify database access controls are properly enforced
  7. Confirm the privileged database account now requires authentication
Caveat Standard upgrade precautions apply - test in staging first, backup before upgrade

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-42473 — 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-42473 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