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

> Local attackers can escalate privileges to SYSTEM in Robotmk if automated Python environment setup is enabled, allowing unauthorized control over shared environments.

- **Severity:** High 7.8 (`CVSS:3.1/AC:L/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:** 4 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-7q6c-8c2j-p7xp

## What is CVE-2024-39934?

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

### Official description

Robotmk before 2.0.1 allows a local user to escalate privileges (e.g., to SYSTEM) if automated Python environment setup is enabled, because the "shared holotree usage" feature allows any user to edit any Python environment.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2024-39934 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-39934 is a high-severity vulnerability in n/a, published on 4 Jul 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-39934 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-39934/ (Markdown: https://insights.sbomify.com/CVE-2024-39934/index.md)
```

## Sources

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

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