# CVE-2024-39708: Privilege escalation in n/a

> A local attacker can escalate privileges by placing a malicious DLL in a temporary directory loaded by the Delinea Privilege Manager Agent.

- **Severity:** High 7.0 (`CVSS:3.1/AC:H/AV:L/A:H/C:H/I:H/PR:L/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jun 2024
- **Updated:** 31 Oct 2024
- **Also known as:** GHSA-6744-v55g-mhwj

## What is CVE-2024-39708?

CVE-2024-39708 is a high-severity vulnerability in n/a, published on 27 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2024-39708?


## How do I fix CVE-2024-39708?

No fix has been published for CVE-2024-39708 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-39708 being exploited?

There is no known exploitation of CVE-2024-39708 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-39708 and fix it if it is affected.

What it is: CVE-2024-39708 is a high-severity vulnerability in n/a, published on 27 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-39708 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-39708/ (Markdown: https://insights.sbomify.com/CVE-2024-39708/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-39708
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-39708
- OSV: https://osv.dev/vulnerability/CVE-2024-39708

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-39708/
Summaries are generated and may contain mistakes; the official description above is the record.