CVE-2019-9837
Openid Connect vulnerability
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.
Affected products
Openid Connect. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Openid Connect runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/doorkeeper-gem/doorkeeper-openid_connect/pull/66 · Patch
- github.com/doorkeeper-gem/doorkeeper-openid_connect/blob/master/CHANGELOG.md · Third Party Advisory
- github.com/doorkeeper-gem/doorkeeper-openid_connect/issues/61 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2019-9837
- cve.org/CVERecord?id=CVE-2019-9837
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.