# CVE-2023-1584: Quarkus-oidc: id and access tokens leak via the authorization code flow

> Attackers can intercept ID and access tokens during authorization code flow if insecure HTTP is used, exposing sensitive user data.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Oct 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-6hc9-cf8x-hf83

## What is CVE-2023-1584?

CVE-2023-1584 is a high-severity vulnerability in Red Hat RHINT Service Registry 2.5.4 GA, published on 4 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2023-1584?

4 open source packages ship an affected version, including io.quarkus:quarkus-oidc. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.quarkus:quarkus-oidc` | Maven | All versions | 2.13.0.Final |
| `io.quarkus:quarkus-oidc` | Maven | All versions | 2.13.0.Final |
| `io.quarkus:quarkus-oidc` | Maven | From 3.0.0 | 3.1.0.Final |
| `io.quarkus:quarkus-oidc` | Maven | From 3.0.0 | 3.1.0.Final |

Products: Quarkus Quarkus.

## How do I fix CVE-2023-1584?

Upgrade io.quarkus:quarkus-oidc to a fixed version for your release line: 2.13.0.Final or 3.1.0.Final.

## Is CVE-2023-1584 being exploited?

There is no known exploitation of CVE-2023-1584 in the wild and no public exploit code.

## Other vulnerabilities in Red Hat RHINT Service Registry 2.5.4 GA

- [CVE-2022-4116](https://insights.sbomify.com/CVE-2022-4116/): Code injection in quarkus dev ui config editor (critical 9.8)
- [CVE-2022-2466](https://insights.sbomify.com/CVE-2022-2466/): Quarkus does not terminate HTTP requests header context (critical 9.8)
- [CVE-2024-12225](https://insights.sbomify.com/CVE-2024-12225/): Io.quarkus:quarkus-security-webauthn: quarkus webauthn unexpected authentication bypass (critical 9.1)
- [CVE-2026-39852](https://insights.sbomify.com/CVE-2026-39852/): Quarkus authorization bypass via semicolon path normalization inconsistency (high 8.8)
- [CVE-2022-0981](https://insights.sbomify.com/CVE-2022-0981/): Privilege escalation in quarkus (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-1584 and fix it if it is affected.

What it is: CVE-2023-1584 is a high-severity vulnerability in Red Hat RHINT Service Registry 2.5.4 GA, published on 4 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-1584 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.quarkus:quarkus-oidc (Maven): affected all versions; fixed in 2.13.0.Final
- io.quarkus:quarkus-oidc (Maven): affected all versions; fixed in 2.13.0.Final
- io.quarkus:quarkus-oidc (Maven): affected from 3.0.0; fixed in 3.1.0.Final
- io.quarkus:quarkus-oidc (Maven): affected from 3.0.0; fixed in 3.1.0.Final

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-1584/ (Markdown: https://insights.sbomify.com/CVE-2023-1584/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-1584
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-1584
- OSV: https://osv.dev/vulnerability/CVE-2023-1584

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-1584/
Summaries are generated and may contain mistakes; the official description above is the record.