What is CVE-2023-1584?

CVE-2023-1584 is a high-severity security vulnerability in io.quarkus:quarkus-oidc (maven), affecting versions < 2.13.0.Final. It is fixed in 2.13.0.Final, 3.1.0.Final.

How severe is CVE-2023-1584?

CVE-2023-1584 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of io.quarkus:quarkus-oidc are affected by CVE-2023-1584?

io.quarkus:quarkus-oidc (maven) versions < 2.13.0.Final is affected.

Is there a fix for CVE-2023-1584?

Yes. CVE-2023-1584 is fixed in 2.13.0.Final, 3.1.0.Final. Upgrade to this version or later.

Is CVE-2023-1584 exploitable, and should I be worried?

Whether CVE-2023-1584 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2023-1584 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2023-1584 in io.quarkus:quarkus-oidc

Q: How severe is CVE-2023-1584?

CVE-2023-1584 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of io.quarkus:quarkus-oidc are affected by CVE-2023-1584?

io.quarkus:quarkus-oidc (maven) versions < 2.13.0.Final is affected.

Q: Is there a fix for CVE-2023-1584?

Yes. CVE-2023-1584 is fixed in 2.13.0.Final, 3.1.0.Final. Upgrade to this version or later.

Q: Is CVE-2023-1584 exploitable, and should I be worried?

Whether CVE-2023-1584 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2023-1584 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2023-1584?

Upgrade: io.quarkus:quarkus-oidc to 2.13.0.Final or later, io.quarkus:quarkus-oidc to 3.1.0.Final or later.

Summary

Quarkus OIDC can leak both ID and access tokens

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.

Impact

CVE-2023-1584 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.13.0.Final, 3.1.0.Final); upgrading removes the vulnerable code path.

Affected versions

io.quarkus:quarkus-oidc (< 2.13.0.Final) io.quarkus:quarkus-oidc (>= 3.0.0, < 3.1.0.Final)

Security releases

io.quarkus:quarkus-oidc → 2.13.0.Final (maven) io.quarkus:quarkus-oidc → 3.1.0.Final (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

io.quarkus:quarkus-oidc to 2.13.0.Final or later; io.quarkus:quarkus-oidc to 3.1.0.Final or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2023-1584? CVE-2023-1584 is a high-severity security vulnerability in io.quarkus:quarkus-oidc (maven), affecting versions < 2.13.0.Final. It is fixed in 2.13.0.Final, 3.1.0.Final.
How severe is CVE-2023-1584? CVE-2023-1584 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of io.quarkus:quarkus-oidc are affected by CVE-2023-1584? io.quarkus:quarkus-oidc (maven) versions < 2.13.0.Final is affected.
Is there a fix for CVE-2023-1584? Yes. CVE-2023-1584 is fixed in 2.13.0.Final, 3.1.0.Final. Upgrade to this version or later.
Is CVE-2023-1584 exploitable, and should I be worried? Whether CVE-2023-1584 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2023-1584 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2023-1584?
- Upgrade io.quarkus:quarkus-oidc to 2.13.0.Final or later
- Upgrade io.quarkus:quarkus-oidc to 3.1.0.Final or later