CVE-2020-36327
Bundler vulnerability
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.
Affected products
Bundler, Fedora, Package Manager Configurations. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Bundler runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- bundler.io/blog/2021/02/15/a-more-secure-bundler-we-fixed-our-source-priorities.html · Vendor Advisory
- msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2021-24105 · Patch
- github.com/rubygems/rubygems/issues/3982 · Exploit
- 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-cve-2020-3632 · Exploit
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/M
- nvd.nist.gov/vuln/detail/CVE-2020-36327
- cve.org/CVERecord?id=CVE-2020-36327
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.