Skip to content

Doorkeeper Improper Authentication vulnerability

Moderate severity GitHub Reviewed Published Jun 12, 2023 in doorkeeper-gem/doorkeeper • Updated Dec 9, 2024

Package

bundler doorkeeper (RubyGems)

Affected versions

< 5.6.6

Patched versions

5.6.6

Description

OAuth RFC 8252 says https://www.rfc-editor.org/rfc/rfc8252#section-8.6

the authorization server SHOULD NOT process authorization requests automatically without user consent or interaction, except when the identity of the client can be assured. This includes the case where the user has previously approved an authorization request for a given client id

But Doorkeeper automatically processes authorization requests without user consent for public clients that have been previously approved. Public clients are inherently vulnerable to impersonation, their identity cannot be assured.

Issue doorkeeper-gem/doorkeeper#1589

Fix doorkeeper-gem/doorkeeper#1646

References

@nbulaj nbulaj published to doorkeeper-gem/doorkeeper Jun 12, 2023
Published by the National Vulnerability Database Jun 12, 2023
Published to the GitHub Advisory Database Jun 12, 2023
Reviewed Jun 12, 2023
Last updated Dec 9, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N

EPSS score

0.125%
(48th percentile)

Weaknesses

CVE ID

CVE-2023-34246

GHSA ID

GHSA-7w2c-w47h-789w

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.