bundler 0.8.0
Allows an attacker to inject arbitrary code into your application via any secondary Gem source declared in your Gemfile
critical severity CVE-2016-7954>= 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.
Please note that this vulnerability only applies for Ruby projects using Bundler < 2.0 with Gemfiles having 2 or more "source" lines.
In other words, if the user's Gemfile does not use multiple sources, this vulnerability can be ignored.
Bundler Gem for Ruby install Command Process Listing Local Plaintext Credential Disclosure
high severity OSVDB-115917>= 1.1.rc
Bundler Gem for Ruby contains a flaw that is due to the program listing credential information in plaintext in the install command process listing. This may allow a local attacker to gain access to credential information.
Bundler Gem for Ruby Redirection Remote HTTP Basic Authentication Credential Disclosure
high severity OSVDB-115091>= 1.3.0.pre.8
Bundler Gem for Ruby contains a flaw that is triggered during the redirection to other hosts. This may allow a remote attacker to gain access to HTTP basic authentication credential information.
Bundler Gem for Ruby Missing SSL Certificate Validation MitM Spoofing
high severity OSVDB-115090>= 1.3.0.pre.8
Bundler Gem for Ruby contains a flaw as SSL certificates are not properly validated. By spoofing the SSL server via a certificate that appears valid, an attacker with the ability to intercept network traffic (e.g. MiTM, DNS cache poisoning) can disclose and optionally manipulate transmitted data.
Local Code Execution through Argument Injection via dash leading git url parameter in Gemfile
high severity CVE-2021-43809>= 2.2.33
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. However, if the Gemfile
includes gem
entries that use the git
option with invalid, but seemingly harmless,
values with a leading dash, this can be false.
To handle dependencies that come from a Git repository instead of a registry, Bundler
uses various commands, such as git clone
. These commands are being constructed using
user input (e.g. the repository URL). When building the commands, Bundler versions
before 2.2.33 correctly avoid Command Injection vulnerabilities by passing an array of
arguments instead of a command string. However, there is the possibility that a user
input starts with a dash (-
) and is therefore treated as an optional argument instead
of a positional one. This can lead to Code Execution because some of the commands have
options that can be leveraged to run arbitrary executables.
Since this value comes from the Gemfile
file, it can contain any character, including
a leading dash.
Exploitation
To exploit this vulnerability, an attacker has to craft a directory containing a
Gemfile
file that declares a dependency that is located in a Git repository. This
dependency has to have a Git URL in the form of -u./payload
. This URL will be used to
construct a Git clone command but will be interpreted as the
upload-pack
argument. Then this directory needs to be shared with the victim, who then needs to run
a command that evaluates the Gemfile, such as bundle lock
, inside.
Impact
This vulnerability can lead to Arbitrary Code Execution, which could potentially lead
to the takeover of the system. However, as explained above, the exploitability is very
low, because it requires a lot of user interaction. It still could put developers at
risk when dealing with untrusted files in a way they think is safe, because the exploit
still works when the victim tries to make sure nothing can happen, e.g. by manually
reviewing the Gemfile
(although they would need the weird URL with a leading dash to
not raise any flags).
This kind of attack vector has been used in the past to target security researchers by sending them projects to collaborate on.
Patches
Bundler 2.2.33 has patched this problem by inserting --
as an argument before any
positional arguments to those Git commands that were affected by this issue.
Workarounds
Regardless of whether users can upgrade or not, they should review any untrusted
Gemfile
's before running any bundler
commands that may read them, since they
can contain arbitrary ruby code.
CVE-2013-0334 rubygem-bundler: 'bundle install' may install a gem from a source other than expected
medium severity CVE-2013-0334>= 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. A flaw was found in the way Bundler handled gems available from multiple sources. An attacker with access to one of the sources could create a malicious gem with the same name, which they could then use to trick a user into installing, potentially resulting in execution of code from the attacker-supplied malicious gem.
No officially reported memory leakage issues detected.
This gem version does not have any officially reported memory leaked issues.
Gem version without a license.
Unless a license that specifies otherwise is included, nobody can use, copy, distribute, or modify this library without being at risk of take-downs, shake-downs, or litigation.
This gem version is available.
This gem version has not been yanked and is still available for usage.