Nix before 2.34.7 and Lix before 2.95.2: stack-to-heap overflow when the parser is run on a coroutine stack
NixOS Nix · Lix Project Lix
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| NixOS Nix |
| No fix yet |
| Lix Project Lix |
|
NixOS Nix · Lix Project Lix
| Product | Affected | Fixed in |
|---|---|---|
| NixOS Nix |
| No fix yet |
| Lix Project Lix |
|
≥ 2.94.0 · < 2.94.2≥ 2.95.0 · < 2.95.2| No fix yet |
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).
From the CVE record · mitre
Unbounded recursion in the NAR parser can overflow an unguarded coroutine stack and overwrite heap memory. A user able to connect to the daemon could potentially execute code as the daemon if ASLR hardening is bypassed; the daemon runs as root in multi-user installations. Nix allows all users to connect by default, subject to its allowed-users setting.
Operators running Nix versions from 2.24.4 or Lix versions from 2.93.0 should check whether their installation has the applicable fix.