Uncontrolled Search Path (DLL Hijack)Weakness · CWE-427

CVE-2024-39708

HIGH · 7.0 CVSS v3.1 Published 2024-06-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/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
An issue was discovered in the Agent in Delinea Privilege Manager (formerly Thycotic Privilege Manager) before 12.0.1096 on Windows. Sometimes, a non-administrator user can copy a crafted DLL file to a temporary directory (used by .NET Shadow Copies) such that privilege escalation can occur if the core agent service loads that file.

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

In Delinea Privilege Manager before 12.0.1096, a non-administrator user can copy a crafted malicious DLL to a temporary directory used by .NET Shadow Copies. When the privileged core agent service starts or restarts and loads this DLL from that directory, it executes the attacker's code with elevated (system/service) privileges, achieving privilege escalation.

MitigationUpgrade to Privilege Manager version 12.0.1096 or later. Until patched, restrict write permissions on temporary directories used by .NET Shadow Copies and monitor for unauthorized DLL placement in those locations.

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

CVSS:3.1/AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Privilege Manager version
    Use the product's built-in version check mechanism (such as the About dialog in the management console, or the version display in the agent UI). Compare your installed version to the affected range (any version before 12.0.1096).
    Affected if Your installed version is earlier than 12.0.1096
  2. Identify .NET Shadow Copy temporary directories
    Locate the temporary directories used by .NET Shadow Copies on your system. These are typically created by the .NET framework in locations such as %TEMP% or subdirectories under the installation path.
    Affected if These directories exist on your system and are accessible to non-administrator users
  3. Inspect for unauthorized DLL files
    List all DLL files in the identified temporary directories used by .NET Shadow Copies. Look for any DLLs that were not placed there by legitimate software updates or installations.
    Affected if Any unexpected or suspicious DLL files are present in these directories
  4. Verify directory write permissions
    Examine the permissions on the temporary directories used by .NET Shadow Copies to determine if non-administrator users have write access.
    Affected if Non-administrator users have write permissions to these directories

You are affected if Privilege Manager is installed at a version before 12.0.1096 AND non-administrator users can write to temporary directories used by .NET Shadow Copies where malicious DLLs could be placed.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Privilege Manager version 12.0.1096 or later. Until patched, restrict write permissions on temporary directories used by .NET Shadow Copies and monitor for unauthorized DLL placement in those locations.

Recommended fix Moderate confidence

12.0.1096 or later

  1. Upgrade Delinea Privilege Manager to version 12.0.1096 or later on all affected Windows systems
  2. After upgrading, verify the core agent service is running the updated version
  3. Ensure the temporary directories used by .NET Shadow Copies have appropriate permissions to prevent non-administrator users from writing executable files

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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