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.
Workaround:
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Link | Tags |
|---|---|
| https://access.redhat.com/errata/RHSA-2023:7700 | vendor advisory |
| https://access.redhat.com/security/cve/CVE-2023-6393 | vdb entry vendor advisory |
| https://bugzilla.redhat.com/show_bug.cgi?id=2253113 | vendor advisory issue tracking |