First published: Wed Mar 22 2023(Updated: )
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.
Credit: secalert@redhat.com secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/io.quarkus:quarkus-oidc | >=3.0.0<3.1.0.Final | 3.1.0.Final |
maven/io.quarkus:quarkus-oidc | <2.13.0.Final | 2.13.0.Final |
Quarkus Quarkus | <2.13.8 | |
redhat/quarkus-oidc | <3.1.0. | 3.1.0. |
<2.13.8 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this flaw in Quarkus is CVE-2023-1584.
The severity rating of CVE-2023-1584 is high with a score of 7.5.
The vulnerability in Quarkus OIDC can leak both ID and access tokens in the authorization code flow when an insecure HTTP protocol is used.
Versions up to and exclusive of 3.1.0.Final and up to and exclusive of 2.13.0.Final of Quarkus OIDC are affected by this vulnerability.
Attackers can access sensitive user data directly from the ID token or by using the access token to access user data from the OIDC provider when exploiting the vulnerability in Quarkus OIDC.