CVE-2020-36327Published
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 pri…
Explicit identifiers and source references
These records connect through source-stated identifiers. Shared identifiers or dates alone do not establish shared exposure, root cause or applicability.
CVE-2020-36327 · Microsoft / collected KEV context
cve-program · CVE-2020-36327
- https://github.com/rubygems/rubygems/issues/3982
- https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2021-24105
- 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://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/MWXHK5UUHVSHF7HTHMX6JY3WXDVNIHSL/
Related operational evidence
Explicit CVE identifiersNo related operational record is retained in the current change model.