RubyGems package
bundler
pkg:gem/bundler
Vulnerabilities (5)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2021-43809 | — | < 2.2.33 | 2.2.33 | Dec 8, 2021 | `Bundler` is a package for managing application dependencies in Ruby. In `bundler` versions before 2.2.33, when working with untrusted and apparently harmless `Gemfile`'s, it is not expected that they lead to execution of external code, unless that's explicit in the ruby code ins | ||
| CVE-2020-36327 | — | >= 1.16.0, < 2.2.10 | 2.2.10 | Apr 29, 2021 | Bundler 1.16.0 through 2.2.9 and 2.2.11 through 2.2.16 sometimes chooses a dependency source based on the highest gem version number, which means that a rogue gem found at a public source may be chosen, even if the intended choice was a private gem that is a dependency of another | ||
| CVE-2019-3881 | — | >= 1.14.0, < 2.1.0 | 2.1.0 | Sep 4, 2020 | 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 a | ||
| CVE-2016-7954 | Cri | 9.8 | >= 1.0.0, < 2.0.0 | 2.0.0 | Dec 22, 2016 | Bundler 1.x might allow remote attackers to inject arbitrary Ruby code into an application by leveraging a gem name collision on a secondary source. NOTE: this might overlap CVE-2013-0334. | |
| CVE-2013-0334 | — | < 1.7.0 | 1.7.0 | Oct 31, 2014 | Bundler before 1.7, when multiple top-level source lines are used, allows remote attackers to install arbitrary gems by creating a gem with the same name as another gem in a different source. |
- CVE-2021-43809Dec 8, 2021affected < 2.2.33fixed 2.2.33
`Bundler` is a package for managing application dependencies in Ruby. In `bundler` versions before 2.2.33, when working with untrusted and apparently harmless `Gemfile`'s, it is not expected that they lead to execution of external code, unless that's explicit in the ruby code ins
- CVE-2020-36327Apr 29, 2021affected >= 1.16.0, < 2.2.10fixed 2.2.10
Bundler 1.16.0 through 2.2.9 and 2.2.11 through 2.2.16 sometimes chooses a dependency source based on the highest gem version number, which means that a rogue gem found at a public source may be chosen, even if the intended choice was a private gem that is a dependency of another
- CVE-2019-3881Sep 4, 2020affected >= 1.14.0, < 2.1.0fixed 2.1.0
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 a
- affected >= 1.0.0, < 2.0.0fixed 2.0.0
Bundler 1.x might allow remote attackers to inject arbitrary Ruby code into an application by leveraging a gem name collision on a secondary source. NOTE: this might overlap CVE-2013-0334.
- CVE-2013-0334Oct 31, 2014affected < 1.7.0fixed 1.7.0
Bundler before 1.7, when multiple top-level source lines are used, allows remote attackers to install arbitrary gems by creating a gem with the same name as another gem in a different source.