Quarkus OIDC can leak both ID and access tokens
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2023-1584US | high7.5 | — | ||
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 acc… | ||||
02
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2023:3809WEB
- https://access.redhat.com/errata/RHSA-2023:7653WEB
- https://access.redhat.com/security/cve/CVE-2023-1584WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=2180886WEB
- https://github.com/quarkusio/quarkusPACKAGE
- https://github.com/quarkusio/quarkus/commit/5369d7ff233d3afe84ecd9160c541fba52b38e69WEB
- https://github.com/quarkusio/quarkus/commit/df305ff12386cf28b33567b8d9a18db164f019ddWEB
- https://github.com/quarkusio/quarkus/pull/32192WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan