CVE-2020-36599

lib/omniauth/failure_endpoint.rb in OmniAuth before 1.9.2 (and before 2.0) does not escape the message_key value.

Published: 2022-08-18 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-36599 is rated Moderate Risk (63.2/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 0.58%). Review affected assets and schedule remediation.

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

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

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 2025-11-21 0.47% 0.58% +0.11%
2 2025-11-18 0.58% 0.47% -0.11%
3 2025-11-04 — 0.58% —

Full EPSS history (11 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
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.
 3.9 5.9 [email protected]

Weakness enumeration for CVE-2020-36599

GitHub Security Advisory for CVE-2020-36599

GHSA-pm55-qfxr-h247 · Severity: critical · Ecosystem: rubygems — OmniAuth's `lib/omniauth/failure_endpoint.rb` does not escape `message_key` value

OS Trackers for CVE-2020-36599

vendor priority summary link
debian not yet assigned CVE-2020-36599 not yet assigned priority: Debian including 1 source packages (ruby-omniauth), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2020-36599
ubuntu medium CVE-2020-36599 medium priority: Ubuntu including 1 source packages (ruby-omniauth), 13 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): needs-triage 7, ignored 6. https://ubuntu.com/security/CVE-2020-36599

Affected software / configurations for CVE-2020-36599

Vendor Product Version Raw CPE
omniauth omniauth < 1.9.2 cpe:2.3:a:omniauth:omniauth:*:*:*:*:*:-:*:*
omniauth omniauth 2.0.0 cpe:2.3:a:omniauth:omniauth:2.0.0:pre.rc1:*:*:*:*:*:*

References for CVE-2020-36599

cvelogic Threat Intelligence