CVE-2024-45710
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 · uneditedSolarWinds Platform is susceptible to an Uncontrolled Search Path Element Local Privilege Escalation vulnerability. This requires a low privilege account and local access to the affected node machine.
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 confidenceSolarWinds Platform contains an Uncontrolled Search Path Element vulnerability allowing local privilege escalation. An attacker with low-privilege local access can manipulate the DLL search path to cause the application to load a malicious DLL, escalating to higher privileges. This is a DLL hijacking vulnerability requiring local machine access.
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< 2024.4CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/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.
-
Confirm SolarWinds Platform is installedLook for the SolarWinds Platform installation directory, typically under C:\Program Files\SolarWinds\ in the file system, or check Windows Programs and Features for an entry named 'SolarWinds Platform'Affected if SolarWinds Platform is present on the system
-
Identify the installed versionOpen the Windows Programs and Features list, find SolarWinds Platform, and note the version number displayed, or check for a version file within the SolarWinds installation directoryAffected if The installed version is earlier than 2024.4 (any version < 2024.4)
-
Examine folder permissions on the SolarWinds installation directoryRight-click the main SolarWinds installation folder, select Properties, go to the Security tab, and review which users and groups have Write or Modify permissions to the folder and its subdirectoriesAffected if Low-privilege users (such as standard users or authenticated users) have Write or Modify access to directories within the SolarWinds installation path
The system is affected by CVE-2024-45710 if SolarWinds Platform version 2024.4 or later is not installed AND low-privilege users can write to folders in the SolarWinds installation directory, allowing DLL hijacking.
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.
dbcve · scoped2024.4
Apply the vendor-supplied patch for CVE-2024-45710 from SolarWinds. As a compensating control, ensure strict folder permissions prevent low-privilege users from writing to directories in SolarWinds' DLL search path.
SolarWinds Platform 2024.4 or later
- Review the SolarWinds Platform 2024.4 release notes for upgrade requirements and注意事项
- Download the SolarWinds Platform 2024.4 (or later) update from the SolarWinds customer portal at www.solarwinds.com
- Test the update in a non-production environment before deploying to production
- Apply the update to the affected SolarWinds Platform installation following standard SolarWinds upgrade procedures
- Verify the installation was successful and the service is running correctly
- Confirm the version is now 2024.4 or later using the SolarWinds Platform utilities
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-45710 — 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-45710 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