PatchTheCVEpacman project vulnerabilities
Recent CVEs affecting pacman project products. 2 tracked.
pacman project has 2 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 2. Most recent: 2020-02-24. Highest priority: CVE-2019-18183 (score 67/100).
- CVE-2019-18183 CRITICAL 9.8 UPGRADE MITIGATE pacman before 5.2 is vulnerable to arbitrary command injection in lib/libalpm/sync.c in the apply_deltas() fun
- CVE-2019-18182 CRITICAL 9.8 UPGRADE MITIGATE pacman before 5.2 is vulnerable to arbitrary command injection in conf.c in the download_with_xfercommand() fu
FAQ
How do I fix pacman project vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is pacman project being exploited right now?
None of the tracked pacman project CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which pacman project CVE should I patch first?
CVE-2019-18183 currently ranks highest (67/100): pacman before 5.2 is vulnerable to arbitrary command injection in lib/libalpm/sync.c in the apply_deltas() fun.