Dependency Confusion in Bundler
Bundler 1.16.0 through 2.2.9 and 2.2.11 through 2.2.17 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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2020-36327US | high8.8 | — | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- https://bundler.io/blog/2021/02/15/a-more-secure-bundler-we-fixed-our-source-priorities.htmlWEB
- https://github.com/rubygems/rubygemsPACKAGE
- https://github.com/rubygems/rubygems/blob/master/bundler/CHANGELOG.md#2218-may-25-2021WEB
- https://github.com/rubygems/rubygems/commit/078bf682ac40017b309b5fc69f283ff640e7c129WEB
- https://github.com/rubygems/rubygems/issues/3982WEB
- https://github.com/rubygems/rubygems/pull/4609WEB
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/bundler/CVE-2020-36327.ymlWEB
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MWXHK5UUHVSHF7HTHMX6JY3WXDVNIHSLWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan