CVE-2023-1584GHSA-6HC9-CF8X-HF83
Quarkus-oidc: id and access tokens leak via the authorization code flow
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.13.0.Final, 3.1.0.Final
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- quarkus-oidc
Version range not reported
- io.quarkus/quarkus-oidc
Version range not reported
- quarkus-oidc
Version range not reported
- io.quarkus:quarkus-oidcMaven
fixed in 2.13.0.Final
- io.quarkus:quarkus-oidcMaven
From 3.0.0 · fixed in 3.1.0.Final