CVE-2019-9837 json
Doorkeeper-openid_connect contains Open Redirect
published 2019-03-15 7 y ago modified 2026-06-17 4 mo ago also GHSA-vv4c-g6q7-p3q7 , EUVD-2019-0393
- cvss
- 6.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
Doorkeeper::OpenidConnect (aka the OpenID Connect extension for Doorkeeper) 1.4.x and 1.5.x before 1.5.4 has an open redirect via the redirect_uri field in an OAuth authorization request (that results in an error response) with the 'openid' scope and a prompt=none value. This allows phishing attacks against the authorization flow.
Patch / fix
- rubygems doorkeeper-openid_connect 1.5.4
- openid openid_connect 1.5.4
- ruby-doorkeeper-openid-connect Debian 14, Debian 13, Debian 12 1.5.5-1
debian advisories DEBIAN-CVE-2019-9837
Exploit prediction
1.35% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 6.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
| GitHub | 3.0 | 6.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | doorkeeper-openid_connect | >=1.4.0, <1.5.4 |
1.5.4 |
Classification
- Weakness
-
- CWE-601 URL Redirection to Untrusted Site
References
-
github.com
/doorkeeper-gem/doorkeeper-openid_connect/pull/66
web, patch, third-party-advisory
-
github.com
/doorkeeper-gem/doorkeeper-openid_connect/issues/61
web, third-party-advisory
-
github.com
/doorkeeper-gem/doorkeeper-openid_connect/blob/master/CHANGELOG.md
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2019-9837
advisory
-
github.com
/doorkeeper-gem/doorkeeper-openid_connect
package
Sources
- CVE List CVE-2019-9837
- GitHub Advisory GHSA-vv4c-g6q7-p3q7
- NVD CVE-2019-9837
Fencer Vulns 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.