# CVE-2023-4853: Quarkus: http security policy bypass > Attackers can bypass HTTP security policies in Quarkus to access unauthorized endpoints or cause denial of service. - **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 20 Sep 2023 - **Updated:** 4 Aug 2026 - **Also known as:** GHSA-4f4r-wgv2-jjvg, RHSA-2023:5479 ## What is CVE-2023-4853? CVE-2023-4853 is a high-severity vulnerability in Redhat Openshift Container Platform, published on 20 Sep 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 where HTTP security policies are not sanitizing certain character permutations correctly when accepting requests, resulting in incorrect evaluation of permissions. This issue could allow an attacker to bypass the security policy altogether, resulting in unauthorized endpoint access and possibly a denial of service. Weakness: CWE-863 (Incorrect Authorization), CWE-148 (Improper Neutralization of Input Leaders) ## Which versions are affected by CVE-2023-4853? 24 open source packages ship an affected version, including io.quarkus:quarkus-csrf-reactive, io.quarkus:quarkus-keycloak-authorization and io.quarkus:quarkus-undertow. It affects 12 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `io.quarkus:quarkus-csrf-reactive` | Maven | All versions | 2.16.11.Final | | `io.quarkus:quarkus-csrf-reactive` | Maven | All versions | 2.16.11.Final | | `io.quarkus:quarkus-csrf-reactive` | Maven | From 3.0.0 | 3.2.6.Final | | `io.quarkus:quarkus-csrf-reactive` | Maven | From 3.0.0 | 3.2.6.Final | | `io.quarkus:quarkus-csrf-reactive` | Maven | From 3.3.0 | 3.3.3 | | `io.quarkus:quarkus-csrf-reactive` | Maven | From 3.3.0 | 3.3.3 | | `io.quarkus:quarkus-keycloak-authorization` | Maven | All versions | 2.16.11.Final | | `io.quarkus:quarkus-keycloak-authorization` | Maven | All versions | 2.16.11.Final | | `io.quarkus:quarkus-keycloak-authorization` | Maven | From 3.0.0 | 3.2.6.Final | | `io.quarkus:quarkus-keycloak-authorization` | Maven | From 3.0.0 | 3.2.6.Final | | `io.quarkus:quarkus-keycloak-authorization` | Maven | From 3.3.0 | 3.3.3 | | `io.quarkus:quarkus-keycloak-authorization` | Maven | From 3.3.0 | 3.3.3 | | `io.quarkus:quarkus-undertow` | Maven | All versions | 2.16.11.Final | | `io.quarkus:quarkus-undertow` | Maven | All versions | 2.16.11.Final | | `io.quarkus:quarkus-undertow` | Maven | From 3.0.0 | 3.2.6.Final | | `io.quarkus:quarkus-undertow` | Maven | From 3.0.0 | 3.2.6.Final | | `io.quarkus:quarkus-undertow` | Maven | From 3.3.0 | 3.3.3 | | `io.quarkus:quarkus-undertow` | Maven | From 3.3.0 | 3.3.3 | | `io.quarkus:quarkus-vertx-http` | Maven | All versions | 2.16.11.Final | | `io.quarkus:quarkus-vertx-http` | Maven | All versions | 2.16.11.Final | | `io.quarkus:quarkus-vertx-http` | Maven | From 3.0.0 | 3.2.6.Final | | `io.quarkus:quarkus-vertx-http` | Maven | From 3.0.0 | 3.2.6.Final | | `io.quarkus:quarkus-vertx-http` | Maven | From 3.3.0 | 3.3.3 | | `io.quarkus:quarkus-vertx-http` | Maven | From 3.3.0 | 3.3.3 | | `openshift-serverless-clients` | Red Hat:serverless:1.0::el8 | All versions | 0:1.9.2-3.el8 | Products: Quarkus Quarkus, Redhat Build of Optaplanner, Redhat Build of Quarkus, Redhat Decision Manager, Redhat Integration Camel K, Redhat Integration Camel Quarkus, Redhat Integration Service Registry, Redhat Jboss Middleware, Redhat Jboss Middleware Text-Only Advisories, Redhat Openshift Container Platform, Redhat Openshift Serverless, Redhat Process Automation Manager. ## How do I fix CVE-2023-4853? Upgrade io.quarkus:quarkus-csrf-reactive to a fixed version for your release line: 2.16.11.Final, 3.2.6.Final or 3.3.3. ## Is CVE-2023-4853 being exploited? There is no known exploitation of CVE-2023-4853 in the wild and no public exploit code. ## Other vulnerabilities in Redhat Openshift Container Platform - [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-4853 and fix it if it is affected. What it is: CVE-2023-4853 is a high-severity vulnerability in Redhat Openshift Container Platform, published on 20 Sep 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-4853 in the wild and no public exploit code. Affected packages and fixed versions: - io.quarkus:quarkus-csrf-reactive (Maven): affected all versions; fixed in 2.16.11.Final - io.quarkus:quarkus-csrf-reactive (Maven): affected all versions; fixed in 2.16.11.Final - io.quarkus:quarkus-csrf-reactive (Maven): affected from 3.0.0; fixed in 3.2.6.Final - io.quarkus:quarkus-csrf-reactive (Maven): affected from 3.0.0; fixed in 3.2.6.Final - io.quarkus:quarkus-csrf-reactive (Maven): affected from 3.3.0; fixed in 3.3.3 - io.quarkus:quarkus-csrf-reactive (Maven): affected from 3.3.0; fixed in 3.3.3 - io.quarkus:quarkus-keycloak-authorization (Maven): affected all versions; fixed in 2.16.11.Final - io.quarkus:quarkus-keycloak-authorization (Maven): affected all versions; fixed in 2.16.11.Final - io.quarkus:quarkus-keycloak-authorization (Maven): affected from 3.0.0; fixed in 3.2.6.Final - io.quarkus:quarkus-keycloak-authorization (Maven): affected from 3.0.0; fixed in 3.2.6.Final - io.quarkus:quarkus-keycloak-authorization (Maven): affected from 3.3.0; fixed in 3.3.3 - io.quarkus:quarkus-keycloak-authorization (Maven): affected from 3.3.0; fixed in 3.3.3 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-4853/ (Markdown: https://insights.sbomify.com/CVE-2023-4853/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-4853 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-4853 - OSV: https://osv.dev/vulnerability/CVE-2023-4853 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-4853/ Summaries are generated and may contain mistakes; the official description above is the record.