CVE-2019-9686
Pacman Project Pacman vulnerability
pacman before 5.1.3 allows directory traversal when installing a remote package via a specified URL "pacman -U <url>" due to an unsanitized file name received from a Content-Disposition header. pacman renames the downloaded package file to match the name given in this header. However, pacman did not sanitize this name, which may contain slashes, before calling rename(). A malicious server (or a network MitM if downloading over HTTP) can send a Content-Disposition header to make pacman place the file anywhere in the filesystem, potentially leading to arbitrary root code execution. Notably, this bypasses pacman's package signature checking. This occurs in curl_download_internal in lib/libalpm/dload.c.
Affected products
Pacman. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Pacman Project Pacman runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- git.archlinux.org/pacman.git/commit/?id=9702703633bec2c007730006de2aeec8587dfc84 · Patch
- git.archlinux.org/pacman.git/commit/?id=d197d8ab82cf10650487518fb968067897a12775 · Patch
- git.archlinux.org/pacman.git/commit/?h=release/5.1.x&id=1bf767234363f7ad5933af3f7ce267c123 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2019-9686
- cve.org/CVERecord?id=CVE-2019-9686
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.