APT root code execution via unverified package installation
Debian APT · Ubuntu APT
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Debian APT |
| No fix yet |
| Ubuntu APT |
|
Debian APT · Ubuntu APT
| Product | Affected | Fixed in |
|---|---|---|
| Debian APT |
| No fix yet |
| Ubuntu APT |
|
≥ 1.6.0 · < 1.6.19+esm1≥ 2.0.0 · < 2.0.12+esm1≥ 2.4.0 · < 2.4.15ubuntu0.1≥ 2.8.0 · < 2.8.4ubuntu0.1| No fix yet |
On Debian, Ubuntu, and derivative Linux distributions, an on-path attacker who can manipulate the HTTP traffic (including a malicious mirror or proxy) between an APT client and an archive server triggered by a package install can trick the client into installing an attacker-controlled unverified package and achieve remote code execution with root privileges.
The vulnerability is caused by the reuse of hard links and requires the client to follow redirects and retry the download of package files. It requires the client to have a non-zero Acquire::Retries configuration setting; the value 3 is the default starting with Debian 12 (bookworm) and Ubuntu 22.04 LTS (Jammy Jellyfish), so older releases are unaffected in a default configuration
From the CVE record · canonical
APT on Debian, Ubuntu, and derivative distributions can install an unverified, attacker-controlled package, allowing code execution as root. An on-path attacker, such as a malicious mirror or proxy, must manipulate HTTP traffic during a package install. The client must follow redirects, retry a package download, and have a non-zero Acquire::Retries setting; 3 is the default from Debian 12 and Ubuntu 22.04 LTS onward.
Engineers running APT on Debian 12 or later, Ubuntu 22.04 LTS or later, or derivative distributions should check their systems; older releases can also be affected if Acquire::Retries is non-zero.