CVE-2024-2097
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 · uneditedAn authenticated malicious client can send a special LINQ query to execute arbitrary code remotely (RCE) on the SCM server from List control, and execute the arbitrary code on the same system where SCMArchivedEventViewerTool is installed in the case of SCM Tools.
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 · moderate confidenceAn authenticated attacker can send specially crafted LINQ queries through the List control in SCM (likely SolarWinds Serv-U or similar) to achieve remote code execution on the SCM server. The vulnerability also affects systems with SCMArchivedEventViewerTool installed, allowing arbitrary code execution on those systems.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if SolarWinds Serv-U (SCM) is installedCheck the installed programs list or examine common installation paths such as C:\Program Files\SolarWinds\Serv-U for Windows or /opt/serv-u for Linux. Look for Serv-U or SCM executable files and note the exact version number displayed in the program properties.Affected if Serv-U or SCM software is present on the system and the version is lower than the vendor-published patched version.
-
Identify if SCMArchivedEventViewerTool is installedCheck the installed programs list or examine the Serv-U installation directory for the SCMArchivedEventViewerTool component. This tool is typically bundled with the main SCM installation.Affected if SCMArchivedEventViewerTool is present on the system and the parent SCM installation is not patched to the vendor-fixed version.
-
Verify the installed SCM version against vendor patchesLocate the exact version number of the Serv-U SCM installation through the program's About or Help section, or by right-clicking the executable and selecting Properties. Compare this version to the vendor's security advisory for CVE-2024-2097 to determine if it predates the fix.Affected if The installed version predates the security patch released for CVE-2024-2097.
-
Confirm administrative access to SCM List control is possibleDetermine if the SCM web interface or administrative console exposes the List control functionality. This is a standard feature in Serv-U SCM; the vulnerability is exploitable through authenticated access to this control.Affected if The List control feature is accessible to authenticated users in the SCM administrative interface.
A system is affected if it runs an unpatched version of SolarWinds Serv-U (SCM) or has SCMArchivedEventViewerTool installed, where authenticated users can access the List control feature.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataRestrict SCM administrative access to trusted authenticated users only, apply vendor patches when available, and implement network segmentation to limit exposure. Input validation on LINQ queries should be implemented to prevent injection.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2097 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-2097 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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