Insecure path handling in Bundler
Bundler prior to 2.1.0 uses a predictable path in `/tmp/`, created with insecure permissions as a storage location for gems, if locations under the user's home directory are not available. If Bundler is used in a scenario where the user does not have a writable home directory, an attacker could place malicious code in this directory that would be later loaded and executed.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2019-3881US | high7.8 | — | ||
Bundler prior to 2.1.0 uses a predictable path in /tmp/, created with insecure permissions as a storage location for gems, if locations under the user's home directory are not avai… | ||||
02
references
External citations — patches, advisories, analysis.
- https://bugzilla.redhat.com/show_bug.cgi?id=1651826WEB
- https://github.com/advisories/GHSA-g98m-96g9-wfjqADVISORY
- https://github.com/rubygems/bundlerPACKAGE
- https://github.com/rubygems/bundler/issues/6501WEB
- https://github.com/rubygems/bundler/pull/7416/commits/65cfebb041c454c246aaf32a177b0243915a9998WEB
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/bundler/CVE-2019-3881.ymlWEB
- https://nvd.nist.gov/vuln/detail/CVE-2019-3881ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan