CVE-2019-9837
First published: Fri Mar 15 2019(Updated: )
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.
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| OpenID Connect | >=1.4.0<1.5.4 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2019-9837?
CVE-2019-9837 is considered a high severity vulnerability due to its potential to facilitate phishing attacks.
How do I fix CVE-2019-9837?
To fix CVE-2019-9837, upgrade the Doorkeeper::OpenidConnect extension to version 1.5.4 or later.
What impact does CVE-2019-9837 have on my application?
CVE-2019-9837 allows attackers to exploit open redirects via the redirect_uri field, potentially leading to phishing risks.
Which versions of Doorkeeper::OpenidConnect are affected by CVE-2019-9837?
CVE-2019-9837 affects Doorkeeper::OpenidConnect versions 1.4.x and 1.5.x prior to 1.5.4.
Is CVE-2019-9837 specific to certain environments?
CVE-2019-9837 is not limited to specific environments and can affect any application using vulnerable versions of the Doorkeeper::OpenidConnect extension.
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/references
- agent/weakness
- agent/remedy
- agent/description
- agent/first-publish-date
- agent/author
- agent/last-modified-date
- agent/softwarecombine
- agent/event
- agent/source
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- collector/nvd-index
- vendor/openid
- canonical/openid connect
- version/openid connect/1.4.0