Description
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.
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 16.04 LTS | bundler | No fix yet | — |
Show 1 more (older releases, extended support, other products)Fewer releases
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu Pro 18.04 LTS | bundler | No fix yet | — |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| RubyGems | bundler | >= 1.0.0, < 2.0.0 | 2.0.0 | GHSA-jvgm-pfqv-887x |
References
- 93423 vdb-entry
- https://github.com/bundler/bundler/issues/5062
- http://collectiveidea.com/blog/archives/2016/10/06/bundlers-multiple-source-security-vulnerability/
- https://bugzilla.redhat.com/show_bug.cgi?id=1381951
- [oss-security] 20161004 Re: Re: CVE request for code execution via gem name collission in bundler (was Re: CVE Request) mailing-list
- [oss-security] 20161004 Re: CVE request for code execution via gem name collission in bundler (was Re: CVE Request) mailing-list
- [oss-security] 20161004 Re: Re: CVE request for code execution via gem name collission in bundler (was Re: CVE Request) mailing-list
- https://github.com/bundler/bundler/issues/5051