CVE-2016-7954: Code Injection
A vulnerability was found in Bundler. Bundler allows the user to specify sources from which Ruby gems are installed. If a secondary source is specified, even if scoped to a specific gem, that source is silently applied to all declared gems. This allows an attacker to introduce arbitrary code into an application via gem name collision on the secondary source, which will unexpectedly (and without warning) take priority over the primary source.
CVE request:
http://seclists.org/oss-sec/2016/q4/18
CVE assignment:
http://seclists.org/oss-sec/2016/q4/20
References:
http://seclists.org/oss-sec/2016/q4/25
Other sources
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.
— MITRE
Affected Software
Remediation
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2016-7954?
The severity of CVE-2016-7954 is classified as high due to the risk of arbitrary code execution.
How do I fix CVE-2016-7954?
To fix CVE-2016-7954, upgrade Bundler to version 1.10.6 or later.
What systems are affected by CVE-2016-7954?
CVE-2016-7954 affects Bundler versions from 1.0.0 through 1.10.5.
What type of vulnerability is CVE-2016-7954?
CVE-2016-7954 is a dependency confusion vulnerability that allows for code injection.
Is there a workaround for CVE-2016-7954?
A recommended workaround for CVE-2016-7954 is to avoid using multiple gem sources until the vulnerability is patched.