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
Link | Resource |
---|---|
https://bundler.io/blog/2021/02/15/a-more-secure-bundler-we-fixed-our-source-priorities.html | Vendor Advisory |
https://github.com/rubygems/rubygems/issues/3982 | Exploit Issue Tracking Third Party Advisory |
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/MWXHK5UUHVSHF7HTHMX6JY3WXDVNIHSL/ | |
https://mensfeld.pl/2021/02/rubygems-dependency-confusion-attack-side-of-things/ | Third Party Advisory |
https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2021-24105 | Patch Vendor Advisory |
https://www.zofrex.com/blog/2021/04/29/bundler-still-vulnerable-dependency-confusion-cve-2020-36327/ | Exploit Third Party Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: mitre
Published: 2021-04-29T02:28:54
Updated: 2021-07-29T02:06:19
Reserved: 2021-04-29T00:00:00
Link: CVE-2020-36327
JSON object: View
NVD Information
Status : Modified
Published: 2021-04-29T03:15:08.710
Modified: 2023-11-07T03:22:14.687
Link: CVE-2020-36327
JSON object: View
Redhat Information
No data.
CWE