Quarkus OIDC can leak both ID and access tokens

2023-10-0412:30:14

Google

osv.dev

quarkus

oidc

tokens leakage

authorization code flow

insecure http

attackers

sensitive data

user data

oidc provider services

passwords

7.5 High

CVSS3

Attack Vector

NETWORK

Attack Complexity

LOW

Privileges Required

NONE

User Interaction

NONE

Scope

UNCHANGED

Confidentiality Impact

HIGH

Integrity Impact

NONE

Availability Impact

NONE

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

0.001 Low

EPSS

Percentile

30.6%

JSON

A flaw was found in Quarkus. Quarkus OIDC can leak both ID and access tokens in the authorization code flow when an insecure HTTP protocol is used, which can allow attackers to access sensitive user data directly from the ID token or by using the access token to access user data from OIDC provider services. Please note that passwords are not stored in access tokens.

CPENameOperatorVersion
io.quarkus:quarkus-oidceq2.11.1.Final
io.quarkus:quarkus-oidceq1.3.0.Alpha1
io.quarkus:quarkus-oidceq0.25.0
io.quarkus:quarkus-oidceq1.7.0.CR1
io.quarkus:quarkus-oidceq2.6.0.CR1
io.quarkus:quarkus-oidceq2.2.5.Final
io.quarkus:quarkus-oidceq2.9.0.CR1
io.quarkus:quarkus-oidceq2.0.0.Alpha3
io.quarkus:quarkus-oidceq1.8.2.Final
io.quarkus:quarkus-oidceq2.2.4.Final

Name	Operator	Version
io.quarkus:quarkus-oidc	eq	2.11.1.Final
io.quarkus:quarkus-oidc	eq	1.3.0.Alpha1
io.quarkus:quarkus-oidc	eq	0.25.0
io.quarkus:quarkus-oidc	eq	1.7.0.CR1
io.quarkus:quarkus-oidc	eq	2.6.0.CR1
io.quarkus:quarkus-oidc	eq	2.2.5.Final
io.quarkus:quarkus-oidc	eq	2.9.0.CR1
io.quarkus:quarkus-oidc	eq	2.0.0.Alpha3
io.quarkus:quarkus-oidc	eq	1.8.2.Final
io.quarkus:quarkus-oidc	eq	2.2.4.Final