What is CVE-2023-5675?

CVE-2023-5675 is a medium-severity improper authentication vulnerability in io.quarkus:quarkus-resteasy-reactive-common-deployment (maven), affecting versions < 3.2.10.Final. It is fixed in 3.2.10.Final, 3.6.9, 3.7.1. The application does not adequately verify the identity of a user, device, or process before granting access.

How severe is CVE-2023-5675?

CVE-2023-5675 has a CVSS score of 6.5 (Medium). 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 packages are affected by CVE-2023-5675?

io.quarkus:quarkus-resteasy-reactive-common-deployment (maven) versions < 3.2.10.Final; io.quarkus:quarkus-resteasy-reactive-common (maven) versions < 3.2.10.Final.

Is there a fix for CVE-2023-5675?

Yes. CVE-2023-5675 is fixed in 3.2.10.Final, 3.6.9, 3.7.1. Upgrade to this version or later.

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

Whether CVE-2023-5675 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-5675 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-5675

Q: How severe is CVE-2023-5675?

CVE-2023-5675 has a CVSS score of 6.5 (Medium). 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: Is there a fix for CVE-2023-5675?

Yes. CVE-2023-5675 is fixed in 3.2.10.Final, 3.6.9, 3.7.1. Upgrade to this version or later.

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

Whether CVE-2023-5675 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-5675 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-5675?

Upgrade: io.quarkus:quarkus-resteasy-reactive-common-deployment to 3.2.10.Final or later, io.quarkus:quarkus-resteasy-reactive-common to 3.2.10.Final or later, io.quarkus:quarkus-resteasy-reactive-common-deployment to 3.6.9 or later, io.quarkus:quarkus-resteasy-reactive-common to 3.6.9 or later, io.quarkus:quarkus-resteasy-reactive-common-deployment to 3.7.1 or later, io.quarkus:quarkus-resteasy-reactive-common to 3.7.1 or later.

Summary

Quarkus: authorization flaw in quarkus resteasy reactive and classic

A flaw was found in Quarkus. When a Quarkus RestEasy Classic or Reactive JAX-RS endpoint has its methods declared in the abstract Java class or customized by Quarkus extensions using the annotation processor, the authorization of these methods will not be enforced if it is enabled by either 'quarkus.security.jaxrs.deny-unannotated-endpoints' or 'quarkus.security.jaxrs.default-roles-allowed' properties.

While backports of this fix exist in versions 3.6.9 and 3.7.1 users of older versions are encouraged to update to the 3.8.x LTS branch.

Impact

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2023-5675 has a CVSS score of 6.5 (Medium). 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 (3.2.10.Final, 3.6.9, 3.7.1); upgrading removes the vulnerable code path.

Affected versions

io.quarkus:quarkus-resteasy-reactive-common-deployment (< 3.2.10.Final) io.quarkus:quarkus-resteasy-reactive-common (< 3.2.10.Final) io.quarkus:quarkus-resteasy-reactive-common-deployment (>= 3.3.0, < 3.6.9) io.quarkus:quarkus-resteasy-reactive-common (>= 3.3.0, < 3.6.9) io.quarkus:quarkus-resteasy-reactive-common-deployment (>= 3.7.0, < 3.7.1) io.quarkus:quarkus-resteasy-reactive-common (>= 3.7.0, < 3.7.1)

Security releases

io.quarkus:quarkus-resteasy-reactive-common-deployment → 3.2.10.Final (maven) io.quarkus:quarkus-resteasy-reactive-common → 3.2.10.Final (maven) io.quarkus:quarkus-resteasy-reactive-common-deployment → 3.6.9 (maven) io.quarkus:quarkus-resteasy-reactive-common → 3.6.9 (maven) io.quarkus:quarkus-resteasy-reactive-common-deployment → 3.7.1 (maven) io.quarkus:quarkus-resteasy-reactive-common → 3.7.1 (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-resteasy-reactive-common-deployment to 3.2.10.Final or later; io.quarkus:quarkus-resteasy-reactive-common to 3.2.10.Final or later; io.quarkus:quarkus-resteasy-reactive-common-deployment to 3.6.9 or later; io.quarkus:quarkus-resteasy-reactive-common to 3.6.9 or later; io.quarkus:quarkus-resteasy-reactive-common-deployment to 3.7.1 or later; io.quarkus:quarkus-resteasy-reactive-common to 3.7.1 or later

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

Frequently Asked Questions

What is CVE-2023-5675? CVE-2023-5675 is a medium-severity improper authentication vulnerability in io.quarkus:quarkus-resteasy-reactive-common-deployment (maven), affecting versions < 3.2.10.Final. It is fixed in 3.2.10.Final, 3.6.9, 3.7.1. The application does not adequately verify the identity of a user, device, or process before granting access.
How severe is CVE-2023-5675? CVE-2023-5675 has a CVSS score of 6.5 (Medium). 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 packages are affected by CVE-2023-5675?
- io.quarkus:quarkus-resteasy-reactive-common-deployment (maven) (versions < 3.2.10.Final)
- io.quarkus:quarkus-resteasy-reactive-common (maven) (versions < 3.2.10.Final)
Is there a fix for CVE-2023-5675? Yes. CVE-2023-5675 is fixed in 3.2.10.Final, 3.6.9, 3.7.1. Upgrade to this version or later.
Is CVE-2023-5675 exploitable, and should I be worried? Whether CVE-2023-5675 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-5675 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-5675?
- Upgrade io.quarkus:quarkus-resteasy-reactive-common-deployment to 3.2.10.Final or later
- Upgrade io.quarkus:quarkus-resteasy-reactive-common to 3.2.10.Final or later
- Upgrade io.quarkus:quarkus-resteasy-reactive-common-deployment to 3.6.9 or later
- Upgrade io.quarkus:quarkus-resteasy-reactive-common to 3.6.9 or later
- Upgrade io.quarkus:quarkus-resteasy-reactive-common-deployment to 3.7.1 or later
- Upgrade io.quarkus:quarkus-resteasy-reactive-common to 3.7.1 or later