# CVE-2023-34246: Doorkeeper Improper Authentication vulnerability

> Doorkeeper library allows public clients to bypass user consent for previously approved authorization requests, enabling potential impersonation.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Jun 2023
- **Updated:** 13 Feb 2025
- **Also known as:** DEBIAN-CVE-2023-34246, DLA-3494-1, DLA-3989-1, GHSA-7w2c-w47h-789w, UBUNTU-CVE-2023-34246, USN-6210-1

## What is CVE-2023-34246?

CVE-2023-34246 is a medium-severity authentication bypass vulnerability in doorkeeper-gem doorkeeper, published on 12 Jun 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Doorkeeper is an OAuth 2 provider for Ruby on Rails / Grape. Prior to version 5.6.6, Doorkeeper automatically processes authorization requests without user consent for public clients that have been previous approved. Public clients are inherently vulnerable to impersonation, their identity cannot be assured. This issue is fixed in version 5.6.6.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2023-34246?

2 open source packages ship an affected version, including doorkeeper. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `doorkeeper` | RubyGems | All versions | 5.6.6 |
| `doorkeeper` | RubyGems | All versions | 5.6.6 |

Products: Doorkeeper Project Doorkeeper.

## How do I fix CVE-2023-34246?

Upgrade doorkeeper to 5.6.6 or later.

## Is CVE-2023-34246 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-34246 exists.

## Other vulnerabilities in doorkeeper-gem doorkeeper

- [CVE-2016-6582](https://insights.sbomify.com/CVE-2016-6582/): Doorkeeper is vulnerable to replay attacks (critical 9.1)
- [CVE-2020-10187](https://insights.sbomify.com/CVE-2020-10187/): Exposure of Sensitive Information to an Unauthorized Actor in Doorkeeper (high 7.5)
- [CVE-2018-1000211](https://insights.sbomify.com/CVE-2018-1000211/): Doorkeeper subject to Incorrect Permission Assignment (high 7.5)
- [CVE-2014-8144](https://insights.sbomify.com/CVE-2014-8144/): Doorkeeper vulnerable to Cross-site Request Forgery (medium 6.8)
- [CVE-2018-1000088](https://insights.sbomify.com/CVE-2018-1000088/): Doorkeeper is vulnerable to stored XSS and code execution (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-34246 and fix it if it is affected.

What it is: CVE-2023-34246 is a medium-severity authentication bypass vulnerability in doorkeeper-gem doorkeeper, published on 12 Jun 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-34246 exists.

Affected packages and fixed versions:
- doorkeeper (RubyGems): affected all versions; fixed in 5.6.6
- doorkeeper (RubyGems): affected all versions; fixed in 5.6.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-34246/ (Markdown: https://insights.sbomify.com/CVE-2023-34246/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-34246
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-34246
- OSV: https://osv.dev/vulnerability/CVE-2023-34246

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-34246/
Summaries are generated and may contain mistakes; the official description above is the record.