CVE-2024-52867 json
guix-daemon in GNU Guix before 5ab3c4c allows privilege escalation because build outputs are accessible by local users before file metadata…
published last yr. modified 4mo ago also EUVD-2024-45958
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 14%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- gnu guix 5ab3c4c
- guix Debian 11 1.2.0-4+deb11u3
debian advisories DEBIAN-CVE-2024-52867
- guix Ubuntu Pro 22.04 LTS 1.3.0-4ubuntu0.1~esm1
- guix Ubuntu Pro 24.04 LTS 1.4.0-6ubuntu0.1~esm1
ubuntu advisories UBUNTU-CVE-2024-52867
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Is CVE-2024-52867 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AC:H/AV:L/A:H/C:H/I:H/PR:N/S:C/UI:N |
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H |
Affected products
- gnu guix
Classification
- Weakness
-
- CWE-276 Incorrect Default Permissions
References
Sources
- CVE List CVE-2024-52867
- NVD CVE-2024-52867
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.