Quarkus-oidc: id and access tokens leak via the authorization code flow
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| affected |
|
||||||||
| Red Hat | Red Hat build of Quarkus 2.13.8.Final | affected |
|
||||||
| Red Hat | RHINT Service Registry 2.5.4 GA | unaffected | — |
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat build of Quarkus 2.13.8.Final | |||
| io.quarkus/quarkus-oidc:2.13.8.Final-redhat-00004 | cpe:/a:redhat:quarkus:2.13::el8 | RHSA-2023:3809 | 2023-06-29T00:00:00Z |
| RHINT Service Registry 2.5.4 GA | |||
| quarkus-oidc | cpe:/a:redhat:service_registry:2.5 | RHSA-2023:7653 | 2023-12-05T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2023-2675 | 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. |
Github GHSA |
GHSA-6hc9-cf8x-hf83 | Quarkus OIDC can leak both ID and access tokens |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.963% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.