First published: Wed Dec 06 2023(Updated: )
A flaw was found in the Quarkus Cache Runtime. When request processing utilizes a Uni cached using @CacheResult and the cached Uni reuses the initial "completion" context, the processing switches to the cached Uni instead of the request context. This is a problem if the cached Uni context contains sensitive information, and could allow a malicious user to benefit from a POST request returning the response that is meant for another user, gaining access to sensitive data.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/io.quarkus:quarkus-cache | >=3.2.0.CR1<3.2.9.Final | 3.2.9.Final |
maven/io.quarkus:quarkus-cache | >=3.3.0.CR1<3.5.2 | 3.5.2 |
redhat/quarkus | <3.2.9. | 3.2.9. |
redhat/quarkus | <2.13.9. | 2.13.9. |
Redhat Build Of Quarkus | ||
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-6393 is a vulnerability in the Quarkus Cache Runtime that allows for potential invalid reuse of context when @CacheResult on a Uni is used.
CVE-2023-6393 has a severity rating of medium and a CVSS score of 5.3.
CVE-2023-6393 can cause request processing to switch to a cached Uni with reused initial context, leading to potential security issues.
Versions 3.2.0.CR1 to 3.2.9.Final and versions 3.3.0.CR1 to 3.5.2 of Quarkus Cache Runtime are affected by CVE-2023-6393.
To fix CVE-2023-6393, update the Quarkus Cache Runtime to version 3.2.9.Final or newer (if using versions 3.2.0.CR1 to 3.2.9.Final), or update to version 3.5.2 or newer (if using versions 3.3.0.CR1 to 3.5.2).