CVE-2020-36327 Detail

Awaiting Analysis


This vulnerability is currently awaiting analysis.

Description

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.

Severity

CVSS 3.x Severity and Metrics:

CVSS 2.0 Severity and Metrics:

References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because they may have information that would be of interest to you. No inferences should be drawn on account of other sites being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose. NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further, NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about this page to [email protected].

Weakness Enumeration

CWE-ID CWE Name Source

Change History

1 change records found show changes

CVE Modified by MITRE 4/30/2021 5:15:08 PM

Action Type Old Value New Value
Added Reference
https://bundler.io/blog/2021/02/15/a-more-secure-bundler-we-fixed-our-source-priorities.html [No Types Assigned]
Added Reference
https://mensfeld.pl/2021/02/rubygems-dependency-confusion-attack-side-of-things/ [No Types Assigned]
Added Reference
https://www.zofrex.com/blog/2021/04/29/bundler-still-vulnerable-dependency-confusion-cve-2020-36327/ [No Types Assigned]

Quick Info

CVE Dictionary Entry:
CVE-2020-36327
NVD Published Date:
04/28/2021
NVD Last Modified:
04/30/2021
Source:
MITRE