Bug 1687755 (CVE-2019-9686) - CVE-2019-9686 pacman: directory traversal vulnerability in lib/libalpm/dload.c
Summary: CVE-2019-9686 pacman: directory traversal vulnerability in lib/libalpm/dload.c
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2019-9686
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1687756
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-12 10:17 UTC by Dhananjay Arunesh
Modified: 2019-09-29 15:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-10 10:50:30 UTC
Embargoed:


Attachments (Terms of Use)

Description Dhananjay Arunesh 2019-03-12 10:17:18 UTC
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.

Upstream commits:
https://git.archlinux.org/pacman.git/commit/?h=release/5.1.x&id=1bf767234363f7ad5933af3f7ce267c123017bde
https://git.archlinux.org/pacman.git/commit/?id=9702703633bec2c007730006de2aeec8587dfc84

Comment 1 Dhananjay Arunesh 2019-03-12 10:17:29 UTC
Created pacman tracking bugs for this issue:

Affects: fedora-all [bug 1687756]

Comment 2 Product Security DevOps Team 2019-06-10 10:50:30 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.


Note You need to log in before you can comment on or make changes to this bug.