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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XQuarkus
APPQuarkus< 3.20.6.13.21.0 – 3.27.3.1 (bez)3.28.0 – 3.33.1.1 (bez)3.34.0 – 3.34.7 (bez)3.35.0 – 3.35.2 (bez)
Related vulnerabilities
Quarkus WebAuthn: pominięcie uwierzytelnienia przez domyślne endpointy REST
A vulnerability was found in quarkus. This security flaw happens in Dev UI Config Editor which is vulnerable t...
It was found that Quarkus 2.10.x does not terminate HTTP requests header context which may lead to unpredictab...
Apache Maven will follow repositories that are defined in a dependency’s Project Object Model (pom) which may ...
Quarkus is a Java framework for building cloud-native applications. Prior to versions 3.37.0, 3.36.3, 3.33.2.1...