Vulnerabilities
Misconfiguration
Runtime Security
Compliance
CVE Vulnerabilities

CVE-2023-4853

Improper Neutralization of Input Leaders

Published: Sep 20, 2023 | Modified: Nov 21, 2024
CVSS 3.x
8.1
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
8.1 IMPORTANT
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Ubuntu
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2023-4853
CWEhttps://cwe.mitre.org/data/definitions/148.html

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

The product does not properly handle when a leading character or sequence (“leader”) is missing or malformed, or if multiple leaders are used when only one should be allowed.

Affected Software

Name Vendor Start Version End Version
Quarkus Quarkus * 2.16.11 (excluding)
Quarkus Quarkus 3.2.0 (including) 3.2.6 (excluding)
Quarkus Quarkus 3.3.0 (including) 3.3.3 (excluding)
Openshift Serverless 1 on RHEL 8 RedHat openshift-serverless-clients-0:1.9.2-3.el8 *
Red Hat build of OptaPlanner 8 RedHat quarkus-vertx-http *
Red Hat build of Quarkus 2.13.8.SP2 RedHat io.quarkus/quarkus-keycloak-authorization:2.13.8.Final-redhat-00005 *
Red Hat build of Quarkus 2.13.8.SP2 RedHat io.quarkus/quarkus-undertow:2.13.8.Final-redhat-00005 *
Red Hat build of Quarkus 2.13.8.SP2 RedHat io.quarkus/quarkus-vertx-http:2.13.8.Final-redhat-00005 *
Red Hat Camel Extensions for Quarkus 2.13.3-1 RedHat quarkus-vertx-http *
Red Hat OpenShift Serverless 1.30 RedHat openshift-serverless-1/client-kn-rhel8:1.9.2-3 *
Red Hat OpenShift Serverless 1.30 RedHat openshift-serverless-1/ingress-rhel8-operator:1.30.1-1 *
Red Hat OpenShift Serverless 1.30 RedHat openshift-serverless-1/knative-rhel8-operator:1.30.1-1 *
Red Hat OpenShift Serverless 1.30 RedHat openshift-serverless-1/kn-cli-artifacts-rhel8:1.9.2-3 *
Red Hat OpenShift Serverless 1.30 RedHat openshift-serverless-1/serverless-operator-bundle:1.30.1-1 *
Red Hat OpenShift Serverless 1.30 RedHat openshift-serverless-1/serverless-rhel8-operator:1.30.1-1 *
Red Hat OpenShift Serverless 1.30 RedHat openshift-serverless-1/svls-must-gather-rhel8:1.30.1-1 *
Red Hat OpenShift Serverless 1.30 RedHat openshift-serverless-1-tech-preview/logic-data-index-ephemeral-rhel8:1.30.0-5 *
Red Hat OpenShift Serverless 1.30 RedHat openshift-serverless-1-tech-preview/logic-swf-builder-rhel8:1.30.0-6 *
Red Hat OpenShift Serverless 1.30 RedHat openshift-serverless-1-tech-preview/logic-swf-devmode-rhel8:1.30.0-6 *
RHEL-8 based Middleware Containers RedHat rhpam-7/rhpam-kogito-builder-rhel8:7.13.4-3 *
RHEL-8 based Middleware Containers RedHat rhpam-7/rhpam-kogito-rhel8-operator:7.13.4-2 *
RHEL-8 based Middleware Containers RedHat rhpam-7/rhpam-kogito-rhel8-operator-bundle:7.13.4-2 *
RHEL-8 based Middleware Containers RedHat rhpam-7/rhpam-kogito-runtime-jvm-rhel8:7.13.4-3 *
RHEL-8 based Middleware Containers RedHat rhpam-7-tech-preview/rhpam-kogito-runtime-native-rhel8:7.13.4-3 *
RHINT Camel-K-1.10.2 RedHat quarkus-vertx-http *
RHINT Service Registry 2.5.4 GA RedHat quarkus-vertx-http *
RHPAM 7.13.4 async RedHat *

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.

References

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2025 Aqua Security Software Ltd.   Privacy Policy | Terms of Use