| Name | CVE-2019-8320 |
| Description | A Directory Traversal issue was discovered in RubyGems 2.7.6 and later through 3.0.2. Before making new directories or touching files (which now include path-checking code for symlinks), it would delete the target destination. If that destination was hidden behind a symlink, a malicious gem could delete arbitrary files on the user's machine, presuming the attacker could guess at paths. Given how frequently gem is run as sudo, and how predictable paths are on modern systems (/tmp, /usr, etc.), this could likely lead to data loss or an unusable system. |
| Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
| References | DLA-1735-1, DLA-2330-1, DSA-4433-1 |
| Debian Bugs | 925987 |
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|---|---|---|
| jruby (PTS) | buster | 9.1.17.0-3 | fixed |
| buster (security) | 9.1.17.0-3+deb10u1 | fixed | |
| bookworm | 9.3.9.0+ds-8 | fixed | |
| sid, trixie | 9.4.6.0+ds-1 | fixed | |
| ruby2.5 (PTS) | buster | 2.5.5-3+deb10u4 | fixed |
| buster (security) | 2.5.5-3+deb10u6 | fixed | |
| rubygems (PTS) | bullseye | 3.2.5-2 | fixed |
| bookworm | 3.3.15-2 | fixed | |
| sid, trixie | 3.4.20-1 | fixed |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|---|---|---|---|---|---|
| jruby | source | jessie | (not affected) | |||
| jruby | source | stretch | 1.7.26-1+deb9u2 | DLA-2330-1 | ||
| jruby | source | (unstable) | 9.1.17.0-3 | 925987 | ||
| ruby2.1 | source | jessie | 2.1.5-2+deb8u7 | DLA-1735-1 | ||
| ruby2.1 | source | (unstable) | (unfixed) | |||
| ruby2.3 | source | stretch | 2.3.3-1+deb9u6 | DSA-4433-1 | ||
| ruby2.3 | source | (unstable) | (unfixed) | |||
| ruby2.5 | source | (unstable) | 2.5.5-1 | |||
| rubygems | source | (unstable) | 3.2.0~rc.1-1 |
[jessie] - jruby <not-affected> (Vulnerable code introduced later)
https://www.ruby-lang.org/en/news/2019/03/05/multiple-vulnerabilities-in-rubygems/
https://blog.rubygems.org/2019/03/05/security-advisories-2019-03.html
https://github.com/rubygems/rubygems/commit/56c0bbb69e4506bda7ef7f447dfec5db820df20b