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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2016-7954US | critical9.8 | — | ||
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-2… | ||||
02
references
External citations — patches, advisories, analysis.
- http://collectiveidea.com/blog/archives/2016/10/06/bundlers-multiple-source-security-vulnerabilityWEB
- http://www.openwall.com/lists/oss-security/2016/10/04/5WEB
- http://www.openwall.com/lists/oss-security/2016/10/04/7WEB
- http://www.openwall.com/lists/oss-security/2016/10/05/3WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=1381951WEB
- https://collectiveidea.com/blog/archives/2016/10/06/bundlers-multiple-source-security-vulnerabilityWEB
- https://github.com/bundler/bundler/issues/5051WEB
- https://github.com/bundler/bundler/issues/5062WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan