Quarkus OIDC can leak both ID and access tokens in the authorization code flow when 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.
This issue has been addressed in the following products: Red Hat build of Quarkus 2.13.8 Via RHSA-2023:3809 https://access.redhat.com/errata/RHSA-2023:3809
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2023-1584
This issue has been addressed in the following products: RHINT Service Registry 2.5.4 GA Via RHSA-2023:7653 https://access.redhat.com/errata/RHSA-2023:7653