Vulnerability in Omniauth
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 · last modified .
CVSS v3 metric
CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS: 0.011 (65.4th percentile), scored .
Low probability of exploitation in the next 30 days, but still tracked. 65th percentile — 65.4% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.011 · newest: 0.011 · change: +0.000
Affected products
- Omniauth — versions 2.0.0
Weakness classification (CWE)
Public proof-of-concept exploits
References
- github.com/omniauth/omniauth/commit/43a396f181ef7d0ed2ec8291c939c95e3ed3ff00 (Patch, Third Party Advisory)
- rubygems.org/gems/omniauth/versions/1.9.2 (Product)
Frequently asked questions
- What is CVE-2020-36599?
- CVE-2020-36599 is a critical-severity vulnerability in Omniauth, classified under Improper Encoding or Escaping of Output. CVSS score: 9.8/10. Published 2022-08-18.
- How severe is CVE-2020-36599?
- Critical severity. CVSS v3 base score is 9.8 out of 10.
- Is CVE-2020-36599 known to be exploited?
- 2 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.