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

> Local users can escalate privileges because build outputs are accessible before setuid/setgid metadata is applied.

- **Severity:** High 8.1 (`CVSS:3.1/AC:H/AV:L/A:H/C:H/I:H/PR:N/S:C/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Nov 2024
- **Updated:** 20 Nov 2024
- **Also known as:** DEBIAN-CVE-2024-52867, DLA-3959-1, DSA-5805-1, GHSA-9h8f-hjmp-pwxx, UBUNTU-CVE-2024-52867

## What is CVE-2024-52867?

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

### Official description

guix-daemon in GNU Guix before 5ab3c4c allows privilege escalation because build outputs are accessible by local users before file metadata concerns (e.g., for setuid and setgid programs) are properly addressed. The vulnerability can be remediated within the product via certain pull, reconfigure, and restart actions. Both 5ab3c4c and 5582241 are needed to resolve the vulnerability.

Weakness: CWE-276 (Incorrect Default Permissions)

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


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

Apply the vendor's patch.

## Is CVE-2024-52867 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-52867 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-52867 is a high-severity vulnerability in n/a, published on 17 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-52867 exists.

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-52867/ (Markdown: https://insights.sbomify.com/CVE-2024-52867/index.md)
```

## Sources

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

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