A flaw was discovered in the RESTEasy Reactive implementation in Quarkus. Due to security checks for some JAX-RS endpoints being performed after serialization, more processing resources are consumed while the HTTP request is checked. In certain configurations, if an attacker has knowledge of any POST, PUT, or PATCH request paths, they can potentially identify vulnerable endpoints and trigger excessive resource usage as the endpoints process the requests. This can result in a denial of service.
Summary
AIIn certain configurations, security checks for some JAX-RS endpoints in Quarkus RESTEasy Reactive occur after serialization, consuming processing resources before an HTTP request is checked. An attacker who knows a POST, PUT, or PATCH request path can potentially identify vulnerable endpoints and send requests that cause excessive resource usage and denial of service.
Who should check
Teams running the Maven package io.quarkus.resteasy.reactive:resteasy-reactive in versions >=3.8.0.CR1 and <3.8.0, >=3.3.0.CR1 and <3.7.4, or <3.2.11.Final should check their exposure.
What to do
- 1Update to the applicable fixed version: 3.8.0, 3.7.4, or 3.2.11.Final.