critical
9.8
CWE
94
Advisory Published
CVE Published
Updated

CVE-2016-7954: Code Injection

First published: Wed Oct 05 2016(Updated: )

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: <a href="http://seclists.org/oss-sec/2016/q4/18">http://seclists.org/oss-sec/2016/q4/18</a> CVE assignment: <a href="http://seclists.org/oss-sec/2016/q4/20">http://seclists.org/oss-sec/2016/q4/20</a> References: <a href="http://seclists.org/oss-sec/2016/q4/25">http://seclists.org/oss-sec/2016/q4/25</a>

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
BusyBox=1.0.0
BusyBox=1.0.0-beta1
BusyBox=1.0.0-beta10
BusyBox=1.0.0-beta6
BusyBox=1.0.0-beta7
BusyBox=1.0.0-beta8
BusyBox=1.0.0-beta9
BusyBox=1.0.0-rc1
BusyBox=1.0.0-rc2
BusyBox=1.0.0-rc3
BusyBox=1.0.0-rc4
BusyBox=1.0.0-rc5
BusyBox=1.0.0-rc6
BusyBox=1.0.1
BusyBox=1.0.2
BusyBox=1.0.3
BusyBox=1.0.4
BusyBox=1.0.5
BusyBox=1.0.6
BusyBox=1.0.7
BusyBox=1.0.8
BusyBox=1.0.9
BusyBox=1.0.10
BusyBox=1.0.11
BusyBox=1.0.12
BusyBox=1.0.13
BusyBox=1.0.14
BusyBox=1.0.15
BusyBox=1.0.16
BusyBox=1.0.17
BusyBox=1.0.18
BusyBox=1.0.19-rc
BusyBox=1.0.20
BusyBox=1.0.20-rc
BusyBox=1.0.21
BusyBox=1.0.21-rc
BusyBox=1.1-pre
BusyBox=1.1-pre1
BusyBox=1.1-pre10
BusyBox=1.1-pre2
BusyBox=1.1-pre3
BusyBox=1.1-pre4
BusyBox=1.1-pre5
BusyBox=1.1-pre6
BusyBox=1.1-pre7
BusyBox=1.1-pre8
BusyBox=1.1-pre9
BusyBox=1.1-rc
BusyBox=1.1-rc2
BusyBox=1.1-rc3
BusyBox=1.1-rc4
BusyBox=1.1-rc5
BusyBox=1.1-rc6
BusyBox=1.1-rc7
BusyBox=1.1-rc8
BusyBox=1.1.0
BusyBox=1.1.1
BusyBox=1.1.2
BusyBox=1.1.3
BusyBox=1.1.4
BusyBox=1.1.5
BusyBox=1.2.0
BusyBox=1.2.0-pre
BusyBox=1.2.0-pre1
BusyBox=1.2.0-rc
BusyBox=1.2.0-rc2
BusyBox=1.2.1
BusyBox=1.2.2
BusyBox=1.2.3
BusyBox=1.2.4
BusyBox=1.2.5
BusyBox=1.3.0
BusyBox=1.3.0-pre
BusyBox=1.3.0-pre2
BusyBox=1.3.0-pre3
BusyBox=1.3.0-pre4
BusyBox=1.3.0-pre5
BusyBox=1.3.0-pre6
BusyBox=1.3.0-pre7
BusyBox=1.3.0-pre8
BusyBox=1.3.1
BusyBox=1.3.2
BusyBox=1.3.3
BusyBox=1.3.4
BusyBox=1.3.5
BusyBox=1.3.6
BusyBox=1.4.0-pre1
BusyBox=1.4.0-rc1
BusyBox=1.5.0
BusyBox=1.5.0-rc1
BusyBox=1.5.0-rc2
BusyBox=1.5.1
BusyBox=1.5.2
BusyBox=1.5.3
BusyBox=1.6.0
BusyBox=1.6.1
BusyBox=1.6.2
BusyBox=1.6.3
BusyBox=1.6.4
BusyBox=1.6.5
BusyBox=1.6.6
BusyBox=1.6.7
BusyBox=1.7.0
BusyBox=1.7.1
BusyBox=1.7.2
BusyBox=1.7.3
BusyBox=1.7.4
BusyBox=1.7.5
BusyBox=1.7.6
BusyBox=1.7.7
BusyBox=1.7.8
BusyBox=1.7.9
BusyBox=1.7.10
BusyBox=1.7.11
BusyBox=1.7.12
BusyBox=1.7.13
BusyBox=1.7.14
BusyBox=1.7.15
BusyBox=1.8.0
BusyBox=1.8.0-pre
BusyBox=1.8.0-rc
BusyBox=1.8.1
BusyBox=1.8.2
BusyBox=1.8.3
BusyBox=1.8.4
BusyBox=1.8.5
BusyBox=1.8.6
BusyBox=1.8.7
BusyBox=1.8.8
BusyBox=1.8.9
BusyBox=1.9.0
BusyBox=1.9.0-pre
BusyBox=1.9.0-pre1
BusyBox=1.9.0-rc
BusyBox=1.9.1
BusyBox=1.9.2
BusyBox=1.9.3
BusyBox=1.9.4
BusyBox=1.9.5
BusyBox=1.9.6
BusyBox=1.9.7
BusyBox=1.9.8
BusyBox=1.9.9
BusyBox=1.9.10
BusyBox=1.10.0
BusyBox=1.10.0-pre
BusyBox=1.10.0-pre1
BusyBox=1.10.0-pre2
BusyBox=1.10.0-rc
BusyBox=1.10.1
BusyBox=1.10.2
BusyBox=1.10.3
BusyBox=1.10.4
BusyBox=1.10.5
BusyBox=1.10.6
BusyBox=1.11.0
BusyBox=1.11.0-pre1
BusyBox=1.11.0-pre2
BusyBox=1.11.1
BusyBox=1.11.2
BusyBox=1.12.0
BusyBox=1.12.0-pre1
BusyBox=1.12.0-pre2
BusyBox=1.12.0-rc
BusyBox=1.12.0-rc2
BusyBox=1.12.0-rc3
BusyBox=1.12.0-rc4
BusyBox=1.12.1
BusyBox=1.12.2
BusyBox=1.12.3
BusyBox=1.12.4
BusyBox=1.12.5
BusyBox=1.12.6
BusyBox=1.13.0
BusyBox=1.13.0-pre1
BusyBox=1.13.0-rc1
BusyBox=1.13.0-rc2
BusyBox=1.13.1
BusyBox=1.13.2
BusyBox=1.13.3
BusyBox=1.13.4
BusyBox=1.13.5
BusyBox=1.13.6

Remedy

https://github.com/bundler/bundler/issues/5051

Remedy

https://github.com/bundler/bundler/issues/5062

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

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.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203