VulnerableCode Package Details - pkg:ebuild/dev-ruby/bundler@2.2.33

Search for packages

Vulnerability	Summary	Fixed by
This package is not known to be affected by vulnerabilities.

Vulnerability

Summary

Fixed by

This package is not known to be affected by vulnerabilities.

Vulnerability	Summary	Aliases
VCID-dy2a-n93k-yfgd	Dependency Confusion in Bundler Bundler 1.16.0 through 2.2.9 and 2.2.11 through 2.2.17 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 is explicitly depended on by the application.	CVE-2020-36327 GHSA-fp4w-jxhp-m23p
VCID-vsps-vp65-p3cw	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.	CVE-2019-3881 GHSA-g98m-96g9-wfjq
VCID-xbrw-47yv-wqcr	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.	CVE-2021-43809 GHSA-fj7f-vq84-fh43

Vulnerability

Summary

Aliases

VCID-dy2a-n93k-yfgd

Dependency Confusion in Bundler Bundler 1.16.0 through 2.2.9 and 2.2.11 through 2.2.17 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 is explicitly depended on by the application.

CVE-2020-36327
GHSA-fp4w-jxhp-m23p

VCID-vsps-vp65-p3cw

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.

CVE-2019-3881
GHSA-g98m-96g9-wfjq

VCID-xbrw-47yv-wqcr

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.

CVE-2021-43809
GHSA-fj7f-vq84-fh43

Date	Actor	Action	Vulnerability	Source	VulnerableCode Version
2026-04-01T13:10:27.701774+00:00	Gentoo Importer	Fixing	VCID-xbrw-47yv-wqcr	https://security.gentoo.org/glsa/202408-22	38.0.0
2026-04-01T13:10:27.692955+00:00	Gentoo Importer	Fixing	VCID-dy2a-n93k-yfgd	https://security.gentoo.org/glsa/202408-22	38.0.0
2026-04-01T13:10:27.684659+00:00	Gentoo Importer	Fixing	VCID-vsps-vp65-p3cw	https://security.gentoo.org/glsa/202408-22	38.0.0