Skip to content
Fencer Intel
high 7.5

CVE-2023-1584 json

Quarkus-oidc: id and access tokens leak via the authorization code flow

published 3y ago modified 4mo ago also GHSA-6hc9-cf8x-hf83 , EUVD-2023-2675

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 62%
public exploits
0
none known

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.

Patch / fix

  • maven io.quarkus:quarkus-oidc 2.13.0.Final, 3.1.0.Final
  • Red Hat Red Hat build of Quarkus 2.13.8.Final 2.13.8.Final-redhat-00004

Is CVE-2023-1584 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-1584 updated cvss 7.5

quarkus-oidc: ID and access tokens leak via the authorization code flow

  • Red Hat build of Quarkus 2.13.8.Final quarkus-oidc 2.13.8.Final-redhat-00004
    fixed: vendor fix RHSA-2023:3809
  • Red Hat RHINT Service Registry 2.5.4 GA
    fixed: vendor fix RHSA-2023:7653
  • Red Hat build of Quarkus 2.13.8.Final jna 5.8.0, bson 4.7.2, db2 1.17.3, h2 2.1.214, jansi 1.18, jdom 1.1.3, +872 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.96% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven io.quarkus:quarkus-oidc
<2.13.0.Final
>=3.0.0, <3.1.0.Final
2.13.0.Final
3.1.0.Final

Affected products

  • Red Hat Red Hat build of Quarkus 2.13.8.Final
  • Red Hat RHINT Service Registry 2.5.4 GA

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.