Quarkus-oidc: id and access tokens leak via the authorization code flow
21Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 7.5epss 1.0%
probabilidad de explotación
1.0%top 40% de las CVE
explotación observada
noninguna fuente lo reporta
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Productos afectados
quarkus-oidcRed Hat · Red Hat build of Quarkus 2.13.8.FinalRed Hat · RHINT Service Registry 2.5.4 GAReferencias
https://access.redhat.com/errata/RHSA-2023:3809https://access.redhat.com/errata/RHSA-2023:7653https://access.redhat.com/security/cve/CVE-2023-1584https://bugzilla.redhat.com/show_bug.cgi?id=2180886https://github.com/quarkusio/quarkus/pull/32192https://github.com/quarkusio/quarkus/pull/33414