Lucene search

K
BundlerBundler

5 matches found

CVE
CVE
added 2021/04/29 3:15 a.m.335 views

CVE-2020-36327

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 private gem that i...

9.3CVSS8.3AI score0.12083EPSS
CVE
CVE
added 2020/09/04 12:15 p.m.277 views

CVE-2019-3881

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...

7.8CVSS7.4AI score0.00211EPSS
CVE
CVE
added 2021/12/08 7:15 p.m.123 views

CVE-2021-43809

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 inside the Gemfile itself. H...

9.3CVSS7.6AI score0.01811EPSS
CVE
CVE
added 2014/10/31 2:55 p.m.89 views

CVE-2013-0334

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.

5CVSS9.2AI score0.00498EPSS
CVE
CVE
added 2016/12/22 10:59 p.m.59 views

CVE-2016-7954

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.

9.8CVSS9.2AI score0.02776EPSS