Vulnerability in Bundler
CVE-2020-36327
Bundler 1.16.0 through 2.2.9 and 2.2.11 through 2.2.16 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. NOTE: it is not correct to use CVE-2021-24105 for every "Dependency Confusion" issue in every product.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 8.8 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS 0.063, 93.7th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
Public exploits and proof-of-concept code
Also mentioned in 3 other repositories (ARPSyndicate/cvemon, matheuslaidler/Tech-Jekyll-Old, matheuslaidler/TechPage-Vuln-Jekyll-Theme). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- github.com/rubygems/rubygems/issues/3982 (Exploit, Third Party Advisory, Issue Tracking)
- msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2021-24105 (Patch, Vendor Advisory)
- bundler.io/blog/2021/02/15/a-more-secure-bundler-we-fixed-our-source-priorities… (Vendor Advisory)
- mensfeld.pl/2021/02/rubygems-dependency-confusion-attack-side-of-things/ (Third Party Advisory)
- www.zofrex.com/blog/2021/04/29/bundler-still-vulnerable-dependency-confusion-cv… (Exploit, Third Party Advisory)
- FEDORA-2021-36cdab1f8d (vendor-advisory)