CVE-2023-34246Public exploitNetwork attack vector

Public-client impersonation via skipped OAuth consent

Published Jun 12, 2023 · Updated Feb 13, 2025

Improper authentication in Doorkeeper before 5.6.6 allows remote attackers to impersonate a previously approved public OAuth client. Doorkeeper::AuthorizationsController#render_success treats any matching prior token as sufficient to skip consent, without checking whether the client application is confidential. Exploitation requires a resource owner who is logged in and has already approved the public client, after which a client-id-only request receives an authorization code without renewed consent.

CVSS severity4.2
Medium
EPSS probability0.72%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Improper authentication in Doorkeeper before 5.6.6 allows remote attackers to impersonate a previously approved public OAuth client. Doorkeeper::AuthorizationsController#render_success treats any matching prior token as sufficient to skip consent, without checking whether the client application is confidential. Exploitation requires a resource owner who is logged in and has already approved the public client, after which a client-id-only request receives an authorization code without renewed consent.

The record

CVE
CVE-2023-34246
Published
Jun 12, 2023
Updated
Feb 13, 2025
Vendor
Doorkeeper
Product
Doorkeeper
Classifications
CWE-287, T1528
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jun 12, 2023CVE publishedPublication date reported by the CVE source.
  2. Feb 13, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 5.6.6

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Doorkeeper · Doorkeeperversion=< 5.6.6

Published CVSS scores

4.2GitHub, Inc.CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N
6.5NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-287Improper Authentication
T1528Steal Application Access Token

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo