OmniAuth's `lib/omniauth/failure_endpoint.rb` does not escape `message_key` value

published 2022-08-18 4y ago modified 2026-06-17 4mo ago also GHSA-pm55-qfxr-h247 , EUVD-2022-6596

cvss: 9.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.2%; EPSS 1.2% chance of exploitation in 30 days, percentile 68%
public exploits: 0; none known

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

Patch / fix

fixed in 2 distros 1 links 1

rubygems omniauth 1.9.2, 2.0.0
omniauth omniauth 1.9.2

ruby-omniauth Debian 14, Debian 13, Debian 12 2.0.4-2

debian advisories DEBIAN-CVE-2020-36599

github.com/omniauth/omniauth@43a396f commit

Is CVE-2020-36599 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.20% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
rubygems	omniauth	<1.9.2 >=2.0.0.pre.rc1, <2.0.0	1.9.2 2.0.0

Classification

Weakness

CWE-116 Improper Encoding or Escaping of Output

References

github.com /omniauth/omniauth/commit/43a396f181ef7d0ed2ec8291c939c95e3ed3ff00#diff-575abda9deb9b1a77bf534e898a923029b9a61
web, patch, third-party-advisory
rubygems.org /gems/omniauth/versions/1.9.2
web, product
nvd.nist.gov /vuln/detail/CVE-2020-36599
advisory
github.com /omniauth/omniauth
package
github.com /rubysec/ruby-advisory-db/blob/master/gems/omniauth/CVE-2020-36599.yml
web

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.