GoogleOSV:CVE-2020-36327CVE-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.
References
bundler.io/blog/2021/02/15/a-more-secure-bundler-we-fixed-our-source-priorities.html
github.com/rubygems/rubygems/issues/3982
lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/MWXHK5UUHVSHF7HTHMX6JY3WXDVNIHSL/
mensfeld.pl/2021/02/rubygems-dependency-confusion-attack-side-of-things/
msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2021-24105
www.zofrex.com/blog/2021/04/29/bundler-still-vulnerable-dependency-confusion-cve-2020-36327/
Related
