Solarwinds PlatformApplication · Solarwinds

CVE-2024-29001

HIGH · 7.4 CVSS v3.1 Published 2024-04-18
Fix available
A fix is available. Upgrade to 2024.1.1 or later.
See remediation →
74/100
Remediation priority · Elevated

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 SolarWinds Platform SWQL Injection Vulnerability was identified in the user interface. This vulnerability requires authentication and user interaction to be exploited.

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

A SWQL (SolarWinds Query Language) injection vulnerability exists in the SolarWinds Platform user interface. The flaw allows authenticated users to inject malicious SWQL queries through the UI, potentially allowing data exfiltration or unauthorized database manipulation. Exploitation requires both authentication and user interaction (such as clicking a crafted link or submitting malicious input).

MitigationApply the vendor-supplied patch or updated version of SolarWinds Platform. Review user access controls and monitor for suspicious query patterns in the interim.

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
Solarwinds PlatformApplication
Affected:< 2024.1.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
Adjacent
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/UI:R/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 installed SolarWinds Platform version
    Access the SolarWinds Platform web UI and navigate to the About or Support section, typically found under Settings > All Settings > About in the Orion Platform. Alternatively, check the installed software list on the server hosting the SolarWinds Platform or review the version displayed on the login page.
    Affected if The displayed version is earlier than 2024.1.1 (for example, 2023.x, 2022.x, or any release prior to the 2024.1.1 patch).
  2. Confirm SWQL query interface is accessible
    Verify that you can access the SolarWinds Query Language (SWQL) query interface within the SolarWinds Platform. This is typically available through the SWQL Studio tool, Advanced Features in the web UI, or custom SWQL-based views and dashboards.
    Affected if The SWQL query interface is available and you have valid credentials to log in to the SolarWinds Platform.
  3. Review logs for suspicious SWQL query patterns
    Examine the SolarWinds Platform logs, particularly the Web logs and SWQL-related logs, for any unusual or malformed query patterns that may indicate injection attempts. Look for queries containing unexpected syntax, UNION statements, OR conditions with tautologies, or comments used to truncate queries.
    Affected if Logs contain SWQL queries that appear to contain injection payloads or unexpected SQL-like syntax not generated by normal application behavior.

A user is affected if their SolarWinds Platform installation shows a version number lower than 2024.1.1 AND they have authenticated access to the SWQL query interface in the UI.

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

Apply the vendor-supplied patch or updated version of SolarWinds Platform. Review user access controls and monitor for suspicious query patterns in the interim.

Recommended fix High confidence

2024.1.1

  1. Back up the SolarWinds Platform database and configuration before starting the upgrade
  2. Download SolarWinds Platform version 2024.1.1 or later from the official SolarWinds download portal
  3. Stop all SolarWinds services to ensure a clean upgrade environment
  4. Run the installer for version 2024.1.1 and follow the on-screen upgrade wizard
  5. After installation completes, restart all SolarWinds services
  6. Verify the upgrade was successful by logging into the web interface and confirming all services are running
Caveat Review SolarWinds upgrade documentation for any prerequisites or compatibility considerations before upgrading

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

Fix this in Solarwinds Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-29001 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-29001 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