An issue was discovered in Nix before 2.34.7 and Lix before 2.95.2.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.28.7, 2.29.4, 2.30.5, 2.31.5, 2.32.8, and 5 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
An issue was discovered in Nix before 2.34.7 and Lix before 2.95.2. Unbounded recursion in the NAR (Nix Archive) parser could lead to a stack-to-heap overflow when the parser is run on a coroutine stack. The stack is allocated without a guard page, which means that a stack overflow could overwrite memory on the heap and could allow arbitrary code execution as the Nix daemon (run as root in multi-user installations) if ASLR hardening is bypassed. This can be exploited by all users able to connect to the daemon (e.g., in Nix, this is configurable via the allowed-users setting, defaulting to all users). The fixed versions are 2.34.7, 2.33.6, 2.32.8, 2.31.5, 2.30.5, 2.29.4, and 2.28.7 for Nix (introduced in 2.24.4); and 2.95.2, 2.94.2, and 2.93.4 for Lix (introduced in 2.93.0).
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- NixOS Nix
From 2.24.4 · fixed in 2.28.7; From 2.29.0 · fixed in 2.29.4; From 2.30.0 · fixed in 2.30.5; From 2.31.0 · fixed in 2.31.5; From 2.32.0 · fixed in 2.32.8; From 2.33.0 · fixed in 2.33.6; From 2.34.0 · fixed in 2.34.7
- Lix Project Lix
From 2.93.0 · fixed in 2.93.4; From 2.94.0 · fixed in 2.94.2; From 2.95.0 · fixed in 2.95.2