CVE-2023-1584 is a high-severity (CVSS 7.5) Information Exposure vulnerability in io.quarkus:quarkus-oidc. A fix is available for io.quarkus:quarkus-oidc — see the affected versions and patch details below.
Quarkus-oidc: id and access tokens leak via the authorization code flow
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2023-1584 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 376,715 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
io.quarkus:quarkus-oidc☕io.quarkus:quarkus-oidcReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.quarkus:quarkus-oidc | all versions | 2.13.0.Finalio.quarkus:quarkus-oidc:2.13.0.Final |
| ☕Maven | io.quarkus:quarkus-oidc | ≥ 3.0.0&&< 3.1.0.Final | 3.1.0.Finalio.quarkus:quarkus-oidc:3.1.0.Final |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.quarkus:quarkus-oidc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.quarkus:quarkus-oidc to 2.13.0.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-1584 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2023-1584 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2023-1584. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Red Hat Build of Quarkus flaw happens because the cookie contains a token that token could potentially be more useful to attackers than a normal session cookie hijacking attack. Other potentially higher security applications may accept the same token from the cookie, while with a normal session hijacking attack it is…
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat build of Quarkus 2.13.8.Final | io.quarkus/quarkus-oidc:2.13.8.Final-redhat-00004 | RHSA-2023:3809 |
| RHINT Service Registry 2.5.4 GA | quarkus-oidc | RHSA-2023:7653 |
Frequently Asked Questions
Is CVE-2023-1584 in your dependencies?
O3 Security finds CVE-2023-1584 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.