Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-6hc9-cf8x-hf83

HIGH

GHSA-6hc9-cf8x-hf83 is a high-severity (CVSS 7.5) Information Exposure vulnerability in io.quarkus:quarkus-oidc. O3 Security confirms whether GHSA-6hc9-cf8x-hf83 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Quarkus OIDC can leak both ID and access tokens

Also known asCVE-2023-1584
Published
Oct 4, 2023
Updated
May 3, 2024
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

Blast Radius

2 pkgs affected
io.quarkus:quarkus-oidcio.quarkus:quarkus-oidc

Real-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

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
Mavenio.quarkus:quarkus-oidcall versions2.13.0.Final
Mavenio.quarkus:quarkus-oidc3.0.0&&< 3.1.0.Final3.1.0.Final

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.quarkus:quarkus-oidc. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. 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 GHSA-6hc9-cf8x-hf83 is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-6hc9-cf8x-hf83 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-6hc9-cf8x-hf83. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-6hc9-cf8x-hf83 in your dependencies?

O3 detects GHSA-6hc9-cf8x-hf83 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.