Affected: quarkusio quarkus, Red Hat Cryostat 4 on RHEL 9, Red Hat HawtIO HawtIO 4.4.0, Red Hat Build of Apache Camel 4.14 for Quarkus 3.27, Red Hat build of Quarkus 3.20.6.SP1, Red Hat build of Quarkus 3.27.3.SP1, Red Hat Streams for Apache Kafka 2.9.4, Red Hat Streams for Apache Kafka 3.2.1, Red Hat OpenShift Serverless, Red Hat build of Apache Camel 4 for Quarkus 3 and 9 more

Quarkus is a Java framework for building cloud-native applications. In versions prior to 3.20.6.1, 3.27.3.1, 3.33.1.1, 3.35.1.1, 3.34.7, and 3.35.2, a path normalization inconsistency between the security layer and the routing layer allows unauthenticated or lower-privileged users to bypass HTTP path-based authorization policies. Quarkus's security layer performs authorization checks on the raw URL path which preserves matrix parameters (semicolons), while RESTEasy Reactive's routing layer strips matrix parameters before matching endpoints. An attacker can append a semicolon and arbitrary text to a request URL (e.g., /api/admin;anything) to bypass policies protecting /api/admin while still routing to the protected endpoint. This issue has been fixed in versions 3.20.6.1, 3.27.3.1, 3.33.1.1, 3.35.1.1, 3.34.7, and 3.35.2.