CVE-2023-1584: high-severity vulnerability in quarkus-oidc
Quarkus-oidc: id and access tokens leak via the authorization code flow
Published · Updated
Follow this CVE+ Monitor Red Hat build of Quarkus 2.13.8.Final+ Monitor RHINT Service Registry 2.5.4 GA
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.5epss 1.0%
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
Affected products
quarkus-oidcRed Hat · Red Hat build of Quarkus 2.13.8.FinalRed Hat · RHINT Service Registry 2.5.4 GARelated CVEs — quarkus-oidc
In the same product, most dangerous first.
References
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