Open Redirect Affecting ruby-doorkeeper-openid-connect package, versions <1.5.5-1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIAN12-RUBYDOORKEEPEROPENIDCONNECT-1559093
- published17 Mar 2019
- disclosed21 Mar 2019
Introduced: 17 Mar 2019
CVE-2019-9837 (opens in a new tab)How to fix?
Upgrade Debian:12 ruby-doorkeeper-openid-connect to version 1.5.5-1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream ruby-doorkeeper-openid-connect package and not the ruby-doorkeeper-openid-connect package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
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.
References
- https://security-tracker.debian.org/tracker/CVE-2019-9837
- https://github.com/doorkeeper-gem/doorkeeper-openid_connect/blob/master/CHANGELOG.md
- https://github.com/doorkeeper-gem/doorkeeper-openid_connect/issues/61
- https://github.com/doorkeeper-gem/doorkeeper-openid_connect/pull/66
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2019-9837