# CVE-2023-5675: Quarkus: authorization flaw in quarkus resteasy reactive and classic > Attackers can bypass authorization on JAX-RS endpoints defined in abstract classes or extensions when specific security properties are enabled. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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:** 25 Apr 2024 - **Updated:** 20 Nov 2025 - **Also known as:** GHSA-25w4-hfqg-4r52 ## What is CVE-2023-5675? CVE-2023-5675 is a medium-severity missing authorization vulnerability in Red Hat A-MQ Clients 2, published on 25 Apr 2024. 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. 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. Weakness: CWE-285 (Improper Authorization) ## Which versions are affected by CVE-2023-5675? 12 open source packages ship an affected version, including io.quarkus:quarkus-resteasy-reactive-common and io.quarkus:quarkus-resteasy-reactive-common-deployment. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `io.quarkus:quarkus-resteasy-reactive-common` | Maven | All versions | 3.2.10.Final | | `io.quarkus:quarkus-resteasy-reactive-common` | Maven | All versions | 3.2.10.Final | | `io.quarkus:quarkus-resteasy-reactive-common` | Maven | From 3.3.0 | 3.6.9 | | `io.quarkus:quarkus-resteasy-reactive-common` | Maven | From 3.3.0 | 3.6.9 | | `io.quarkus:quarkus-resteasy-reactive-common` | Maven | From 3.7.0 | 3.7.1 | | `io.quarkus:quarkus-resteasy-reactive-common` | Maven | From 3.7.0 | 3.7.1 | | `io.quarkus:quarkus-resteasy-reactive-common-deployment` | Maven | All versions | 3.2.10.Final | | `io.quarkus:quarkus-resteasy-reactive-common-deployment` | Maven | All versions | 3.2.10.Final | | `io.quarkus:quarkus-resteasy-reactive-common-deployment` | Maven | From 3.3.0 | 3.6.9 | | `io.quarkus:quarkus-resteasy-reactive-common-deployment` | Maven | From 3.3.0 | 3.6.9 | | `io.quarkus:quarkus-resteasy-reactive-common-deployment` | Maven | From 3.7.0 | 3.7.1 | | `io.quarkus:quarkus-resteasy-reactive-common-deployment` | Maven | From 3.7.0 | 3.7.1 | ## How do I fix CVE-2023-5675? Upgrade io.quarkus:quarkus-resteasy-reactive-common to a fixed version for your release line: 3.2.10.Final, 3.6.9 or 3.7.1. ## Is CVE-2023-5675 being exploited? There is no known exploitation of CVE-2023-5675 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-5675 and fix it if it is affected. What it is: CVE-2023-5675 is a medium-severity missing authorization vulnerability in Red Hat A-MQ Clients 2, published on 25 Apr 2024. 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-5675 in the wild and no public exploit code. Affected packages and fixed versions: - io.quarkus:quarkus-resteasy-reactive-common (Maven): affected all versions; fixed in 3.2.10.Final - io.quarkus:quarkus-resteasy-reactive-common (Maven): affected all versions; fixed in 3.2.10.Final - io.quarkus:quarkus-resteasy-reactive-common (Maven): affected from 3.3.0; fixed in 3.6.9 - io.quarkus:quarkus-resteasy-reactive-common (Maven): affected from 3.3.0; fixed in 3.6.9 - io.quarkus:quarkus-resteasy-reactive-common (Maven): affected from 3.7.0; fixed in 3.7.1 - io.quarkus:quarkus-resteasy-reactive-common (Maven): affected from 3.7.0; fixed in 3.7.1 - io.quarkus:quarkus-resteasy-reactive-common-deployment (Maven): affected all versions; fixed in 3.2.10.Final - io.quarkus:quarkus-resteasy-reactive-common-deployment (Maven): affected all versions; fixed in 3.2.10.Final - io.quarkus:quarkus-resteasy-reactive-common-deployment (Maven): affected from 3.3.0; fixed in 3.6.9 - io.quarkus:quarkus-resteasy-reactive-common-deployment (Maven): affected from 3.3.0; fixed in 3.6.9 - io.quarkus:quarkus-resteasy-reactive-common-deployment (Maven): affected from 3.7.0; fixed in 3.7.1 - io.quarkus:quarkus-resteasy-reactive-common-deployment (Maven): affected from 3.7.0; fixed in 3.7.1 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-5675/ (Markdown: https://insights.sbomify.com/CVE-2023-5675/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-5675 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-5675 - OSV: https://osv.dev/vulnerability/CVE-2023-5675 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-5675/ Summaries are generated and may contain mistakes; the official description above is the record.