Search for packages
| purl | pkg:gem/bundler@1.3.0.pre.6 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-16du-zvpy-r7g8
Aliases: OSVDB-115091 |
Redirection Remote HTTP Basic Authentication Credential Disclosure This package 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. |
Affected by 4 other vulnerabilities. |
|
VCID-3vzg-f63c-yfe8
Aliases: CVE-2016-7954 GHSA-jvgm-pfqv-887x |
Bundler allows attacker to inject arbitrary code via secondary Gem source 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. |
Affected by 3 other vulnerabilities. |
|
VCID-qrmf-7afx-6yd8
Aliases: CVE-2013-0334 GHSA-49jx-9cmc-xjxm OSV-110004 |
Remote code execution Any Gemfile with multiple top-level `source` lines cannot reliably control the gem server that a particular gem is fetched from. As a result, Bundler might install the wrong gem if more than one source provides a gem with the same name. This is especially possible in the case of Github's legacy gem server, hosted at gems.github.com. An attacker might create a malicious gem on Rubygems.org with the same name as a commonly-used Github gem. From that point forward, running `bundle install` might result in the malicious gem being used instead of the expected gem. |
Affected by 3 other vulnerabilities. |
|
VCID-vsps-vp65-p3cw
Aliases: CVE-2019-3881 GHSA-g98m-96g9-wfjq |
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. |
Affected by 2 other vulnerabilities. |
|
VCID-xbrw-47yv-wqcr
Aliases: CVE-2021-43809 GHSA-fj7f-vq84-fh43 |
Local Code Execution through Argument Injection via dash leading git url parameter in Gemfile. 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. |
Affected by 0 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||