CVE-2020-36327

Exp

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.

Published: 2021-04-29 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2020-36327 is rated High Exploit Risk (81.9/100): CVSS High severity, with high exploitation likelihood (EPSS 25.07%, 96th percentile). Core evidence: 2 public exploit reference(s) are indexed (Exploit-DB). Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2020-36327

EDB-ID Source Kind Published Link
nvd_ref exploit_tag Exploit-DB ↗
nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2020-36327

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-03 27.11% 25.07% -2.04%
2 2026-06-02 24.73% 27.11% +2.38%
3 2026-05-25 24.73%

Full EPSS history (70 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-36327

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
2.8 5.9 [email protected]
9.3 2.0 HIGH
AV:N/AC:M/Au:N/C:C/I:C/A:C Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
8.6 10.0 [email protected]

Weakness enumeration for CVE-2020-36327

GitHub Security Advisory for CVE-2020-36327

GHSA-fp4w-jxhp-m23p · Severity: high · Ecosystem: rubygems — Dependency Confusion in Bundler

OS Trackers for CVE-2020-36327

vendor priority summary link
alpine high CVE-2020-36327: 1 source package rows (ruby-bundler); 3 state rows across 3 repos (3.10-main, 3.11-main, 3.12-main); fixed 0, open 3. https://security.alpinelinux.org/vuln/CVE-2020-36327
debian not yet assigned CVE-2020-36327 not yet assigned priority: Debian including 1 source packages (rubygems), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2020-36327
gentoo normal CVE-2020-36327: 1 GLSA(s) (202408-22), 1 atom(s) (dev-ruby/bundler); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2020-36327
redhat high https://access.redhat.com/security/cve/CVE-2020-36327
suse high CVE-2020-36327 severity important: SUSE including 271 source package names (2.21-61.3:ruby2.5-rubygem-bundler-2.2.34-150000.3.11.1, 2.5-31.57:ruby2.5-rubygem-bundler-2.2.34-150000.3.11.1, …), 351 product×package rows across 81 product lines (Container bci/ruby, Container suse/rmt-server, … (81 product lines)): Known Affected 231, Fixed 103, Known Not Affected 17. https://www.suse.com/security/cve/CVE-2020-36327/
ubuntu medium CVE-2020-36327 medium priority: Ubuntu including 1 source packages (bundler), 16 status rows across 16 suites (bionic, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 10, needs-triage 4, ignored 2. https://ubuntu.com/security/CVE-2020-36327

Affected software / configurations for CVE-2020-36327

Vendor Product Version Raw CPE
bundler bundler >= 1.16.0, < 2.2.10 cpe:2.3:a:bundler:bundler:*:*:*:*:*:ruby:*:*
bundler bundler >= 2.2.11, <= 2.2.16 cpe:2.3:a:bundler:bundler:*:*:*:*:*:ruby:*:*
fedoraproject fedora 34 cpe:2.3:o:fedoraproject:fedora:34:*:*:*:*:*:*:*
microsoft package_manager_configurations cpe:2.3:a:microsoft:package_manager_configurations:-:*:*:*:*:*:*:*

References for CVE-2020-36327

cvelogic Threat Intelligence