Dependency Confusion in Bundler with Implicit Private Dependencies
Published: September 30, 2020
SECURITY IDENTIFIERS
- CVE: CVE-2020-36327 (NVD)
- GHSA: GHSA-fp4w-jxhp-m23p
- Vendor Advisory: https://github.com/rubygems/rubygems/issues/3982
GEM
SEVERITY
CVSS v3.x: 8.8 (High)
UNAFFECTED VERSIONS
< 1.16.0
PATCHED VERSIONS
= 2.2.10
>= 2.2.18
DESCRIPTION
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.
RELATED
- CVE-2021-24105 (NVD)
- https://bundler.io/blog/2021/02/15/a-more-secure-bundler-we-fixed-our-source-priorities.html
- https://mensfeld.pl/2021/02/rubygems-dependency-confusion-attack-side-of-things/
- https://www.zofrex.com/blog/2021/04/29/bundler-still-vulnerable-dependency-confusion-cve-2020-36327/
- https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2021-24105
- https://github.com/rubygems/rubygems/pull/4609