Quarkus: security checks for some inherited endpoints performed after serialization in resteasy reactive may trigger a denial of service
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.2.11.Final, 3.7.4, 3.8.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- quarkus-resteasy-reactive
fixed in 3.2.11.Final; From 3.3.0.CR1 · fixed in 3.7.4
- io.quarkus/quarkus-resteasy-reactive
Version range not reported
- resteasy-reactive
Version range not reported
- io.quarkus.resteasy.reactive:resteasy-reactiveMaven
From 3.8.0.CR1 · fixed in 3.8.0
- io.quarkus.resteasy.reactive:resteasy-reactiveMaven
From 3.3.0.CR1 · fixed in 3.7.4
- io.quarkus.resteasy.reactive:resteasy-reactiveMaven
fixed in 3.2.11.Final