CVE-2023-4853: Quarkus: http security policy bypass

Published Sep 8, 2023
·
Updated

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.

Other sources

Quarkus could allow a remote attacker to bypass security restrictions, caused by improper sanitization of requests. By sending a specially crafted request, an attacker could exploit this vulnerability to bypass the security policy altogether.

— IBM

Quarkus using HTTP security policies was found to not sanitize certain character permutations correctly when accepting requests, resulting in problematic request resolution. An attacker could use this flaw to bypass the security policy altogether, resulting in unauthorized information or function access, and possibly even denial of service.

— Red Hat

Affected Software

34 affected componentsFixes available
redhat/openshift-serverless-clients<0:1.9.2-3.el8
0:1.9.2-3.el8
maven/io.quarkus:quarkus-keycloak-authorization>=3.3.0<3.3.3
3.3.3
maven/io.quarkus:quarkus-keycloak-authorization>=3.0.0<3.2.6.Final
3.2.6.Final
maven/io.quarkus:quarkus-keycloak-authorization<2.16.11.Final
2.16.11.Final
maven/io.quarkus:quarkus-csrf-reactive>=3.3.0<3.3.3
3.3.3
maven/io.quarkus:quarkus-csrf-reactive>=3.0.0<3.2.6.Final
3.2.6.Final
maven/io.quarkus:quarkus-csrf-reactive<2.16.11.Final
2.16.11.Final
maven/io.quarkus:quarkus-undertow>=3.3.0<3.3.3
3.3.3
maven/io.quarkus:quarkus-undertow>=3.0.0<3.2.6.Final
3.2.6.Final
maven/io.quarkus:quarkus-undertow<2.16.11.Final
2.16.11.Final
maven/io.quarkus:quarkus-vertx-http>=3.3.0<3.3.3
3.3.3
maven/io.quarkus:quarkus-vertx-http>=3.0.0<3.2.6.Final
3.2.6.Final
maven/io.quarkus:quarkus-vertx-http<2.16.11.Final
2.16.11.Final
Quarkus Quarkus<2.16.11
Quarkus Quarkus>=3.2.0<3.2.6
Quarkus Quarkus>=3.3.0<3.3.3
redhat Build Of Optaplanner=8.0
redhat Build Of Quarkus>=2.13.0<2.13.8
redhat Decision Manager=7.0
redhat Integration Camel K<1.10.2
redhat Integration Camel Quarkus
redhat Integration Service Registry
redhat Jboss Middleware=1
redhat Openshift Serverless
redhat Openshift Serverless=1.0
redhat Process Automation Manager=7.0
redhat Jboss Middleware Text-only Advisories Middleware=1.0
All of the following
Any of the following
redhat OpenShift Container Platform=4.10
redhat OpenShift Container Platform=4.11
redhat OpenShift Container Platform=4.12
redhat Enterprise Linux=8.0
redhat/quarkus<2.16.11.
2.16.11.
redhat/quarkus<3.2.6.
3.2.6.
redhat/quarkus<3.3.3
3.3.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/openshift-serverless-clients to a version that resolves this vulnerability.

    Fixed in 0:1.9.2-3.el8
  2. Upgrade

    Upgrade maven/io.quarkus:quarkus-keycloak-authorization to a version that resolves this vulnerability.

    Fixed in 3.3.3
  3. Upgrade

    Upgrade maven/io.quarkus:quarkus-keycloak-authorization to a version that resolves this vulnerability.

    Fixed in 3.2.6.Final
  4. Upgrade

    Upgrade maven/io.quarkus:quarkus-keycloak-authorization to a version that resolves this vulnerability.

    Fixed in 2.16.11.Final
  5. Upgrade

    Upgrade maven/io.quarkus:quarkus-csrf-reactive to a version that resolves this vulnerability.

    Fixed in 3.3.3
  6. Upgrade

    Upgrade maven/io.quarkus:quarkus-csrf-reactive to a version that resolves this vulnerability.

    Fixed in 3.2.6.Final
  7. Upgrade

    Upgrade maven/io.quarkus:quarkus-csrf-reactive to a version that resolves this vulnerability.

    Fixed in 2.16.11.Final
  8. Upgrade

    Upgrade maven/io.quarkus:quarkus-undertow to a version that resolves this vulnerability.

    Fixed in 3.3.3
  9. Upgrade

    Upgrade maven/io.quarkus:quarkus-undertow to a version that resolves this vulnerability.

    Fixed in 3.2.6.Final
  10. Upgrade

    Upgrade maven/io.quarkus:quarkus-undertow to a version that resolves this vulnerability.

    Fixed in 2.16.11.Final
  11. Upgrade

    Upgrade maven/io.quarkus:quarkus-vertx-http to a version that resolves this vulnerability.

    Fixed in 3.3.3
  12. Upgrade

    Upgrade maven/io.quarkus:quarkus-vertx-http to a version that resolves this vulnerability.

    Fixed in 3.2.6.Final
  13. Upgrade

    Upgrade maven/io.quarkus:quarkus-vertx-http to a version that resolves this vulnerability.

    Fixed in 2.16.11.Final
  14. Upgrade

    Upgrade redhat/quarkus to a version that resolves this vulnerability.

    Fixed in 2.16.11.
  15. Upgrade

    Upgrade redhat/quarkus to a version that resolves this vulnerability.

    Fixed in 3.2.6.
  16. Upgrade

    Upgrade redhat/quarkus to a version that resolves this vulnerability.

    Fixed in 3.3.3
  17. Compensating control

    Use the mitigations described for Quarkus HTTP security policies: apply a deny wildcard for base paths (e.g., "deny: /*"), then explicitly authenticate/allow specifics within the authenticated paths (e.g., "authenticated: /services/*"), or use path-scoped roles such as "roles-allowed: /services/rbac/*".

Event History

Sep 8, 2023
CVE Published
12:00 AM
Data Sourced
via Red Hat·04:29 PM
DescriptionSeverityAffected Software
Sep 20, 2023
CVE Published
via MITRE·09:47 AM
Data Sourced
via MITRE·09:47 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:15 AM
DescriptionSeverityWeaknessAffected Software
Advisory Published
12:30 PM
Dec 13, 2023
Data Sourced
via IBM·12:00 AM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2023-4853?

CVE-2023-4853 is a vulnerability in Quarkus that allows an attacker to bypass security policies and gain unauthorized access to endpoints.

2

How severe is CVE-2023-4853?

CVE-2023-4853 has a severity rating of 9.8 out of 10, indicating it is critical.

3

Which versions of Quarkus are affected by CVE-2023-4853?

Quarkus versions between 2.16.11 and 3.3.3 are affected by CVE-2023-4853.

4

How can I fix CVE-2023-4853?

To fix CVE-2023-4853, update Quarkus to version 3.3.3 or apply the appropriate patches provided by Red Hat.

5

Where can I find more information about CVE-2023-4853?

You can find more information about CVE-2023-4853 in the references section of the vulnerability report.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203