dbcve.org
FortisoarApplication · Fortinet

CVE-2024-31493

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-03
Fix available
A fix is available. Upgrade to 7.3.1 or later.
See remediation →
71/100
Remediation priority · Elevated
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 removal of sensitive information before storage or transfer vulnerability [CWE-212] in FortiSOAR version 7.3.0, version 7.2.2 and below, version 7.0.3 and below may allow an authenticated low privileged user to read Connector passwords in plain-text via HTTP responses.

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 versions 7.3.0, 7.2.2 and below, and 7.0.3 and below contain a CWE-212 vulnerability where connector passwords are exposed in plain-text within HTTP responses. Authenticated low-privileged users can intercept these responses to retrieve sensitive credential data that should have been masked or encrypted before storage or transfer.

MitigationUpgrade FortiSOAR to a patched version (contact Fortinet for specific patch availability). In the interim, restrict low-privilege user access to connector configuration pages and monitor HTTP traffic for unauthorized credential exposure.

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:>= 7.0.0, < 7.3.1

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/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 FortiSOAR version
    Locate the installed FortiSOAR version in the system administration panel under 'About' or use the command line: 'docker ps' or check the installer metadata. Compare the version number to the affected range: 7.0.0 through 7.3.0 (versions below 7.3.1 are affected).
    Affected if Installed version is 7.0.0 to 7.3.0 inclusive (any version >= 7.0.0 but < 7.3.1)
  2. Verify low-privilege user access to connectors
    Navigate to the connector configuration module. Log in as a low-privileged user (non-admin) and check if they can view or edit connector configurations. Inspect the role permissions under 'Access Management' > 'Roles' to confirm whether the 'Connectors' or 'Configuration' permission is granted to low-privilege roles.
    Affected if Low-privilege or non-admin users have permission to access connector configuration pages
  3. Inspect HTTP responses for plain-text passwords
    Use a web proxy (such as Burp Suite or browser developer tools) to capture HTTP traffic while accessing the connector API endpoints (typically /api/3/connectors or /api/3/connector_configs). Review the JSON response bodies for any password fields that display plaintext values instead of masked characters or encrypted strings.
    Affected if HTTP responses from connector API endpoints contain unmasked, plaintext password values in the response body
  4. Examine connector configuration storage
    If you have database access, query the connector configuration table (commonly named 'connector_config' or similar) to inspect how passwords are stored. Check if password fields contain encrypted values, hashed values, or plaintext strings.
    Affected if Connector passwords are stored in plaintext in the database rather than being encrypted or hashed

You are affected if your FortiSOAR version is 7.0.0 through 7.3.0 AND low-privilege users can access connector configuration, resulting in plaintext password exposure in HTTP responses or stored data.

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.3.1 or later
Fixed in 7.3.1
Interim mitigation

Upgrade FortiSOAR to a patched version (contact Fortinet for specific patch availability). In the interim, restrict low-privilege user access to connector configuration pages and monitor HTTP traffic for unauthorized credential exposure.

Recommended fix High confidence

FortiSOAR 7.3.1 or later

  1. 1. Create a complete backup of the current FortiSOAR installation including database and configuration
  2. 2. Download FortiSOAR version 7.3.1 or later from the Fortinet Customer Support Portal
  3. 3. Review FortiSOAR upgrade documentation for the specific upgrade procedure applicable to your current version
  4. 4. Execute the upgrade following the documented procedure
  5. 5. After upgrade, verify that Connector passwords are no longer exposed in plain-text in HTTP responses
  6. 6. Confirm the fix by testing with a low-privileged authenticated user to ensure passwords are properly redacted
Caveat Review release notes for any configuration or migration requirements between your current version and 7.3.1

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

Fix this in Fortisoar Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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