CVE-2019-9837: Medium severity openid connect vulnerability

Published 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 redirecturi 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 Software

1 affected component
Openid Openid Connect Doorkeeper>=1.4.0<1.5.4

Event History

Mar 15, 2019
CVE Published
via MITRE·11:00 PM
Data Sourced
via MITRE·11:00 PM
Description
Mar 21, 2019
Data Sourced
via NVD·04:01 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

How do I fix CVE-2019-9837?

To fix CVE-2019-9837, upgrade the Doorkeeper::OpenidConnect extension to version 1.5.4 or later.

3

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.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203