Pacman Project Pacman
4 CVEs affecting Pacman Project Pacman. Latest disclosed: 2020-02-24. Critical: 2, High: 1.
| CVE | Severity | Score | Published | Summary |
|---|---|---|---|---|
CVE-2019-18183 | Critical | 9.8 | 2020-02-24 | pacman before 5.2 is vulnerable to arbitrary command injection in lib/libalpm/sync.c in the apply_deltas() function. This can be exploited when unsigned databa… |
CVE-2019-18182 | Critical | 9.8 | 2020-02-24 | pacman before 5.2 is vulnerable to arbitrary command injection in conf.c in the download_with_xfercommand() function. This can be exploited when unsigned datab… |
CVE-2019-9686 | High | 8.8 | 2019-03-11 | 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… |
CVE-2016-5434 | Medium | 5.5 | 2017-01-30 | libalpm, as used in pacman 5.0.1, allows remote attackers to cause a denial of service (infinite loop or out-of-bounds read) via a crafted signature file. |