Quarkus authorization bypass via semicolon path normalization inconsistency
quarkusio quarkus
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| io.quarkus:quarkus-vertx-http Maven |
|
|
quarkusio quarkus
| Product | Affected | Fixed in |
|---|---|---|
| io.quarkus:quarkus-vertx-http Maven |
|
|
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.
From the CVE record · GitHub_M
A path normalization inconsistency between Quarkus security checks and RESTEasy Reactive routing can let unauthenticated or lower-privileged users bypass HTTP path-based authorization. An attacker can send an HTTP request with a semicolon and arbitrary text appended to a protected path, causing it to route to the protected endpoint without matching its authorization policy. No user interaction is required.
Teams running Quarkus applications with Maven io.quarkus:quarkus-vertx-http in the listed affected ranges should check their versions.