Skip to content

Quarkus Cache Runtime exposes sensitive information to an unauthorized actor

Moderate severity GitHub Reviewed Published Dec 6, 2023 to the GitHub Advisory Database • Updated Aug 2, 2024

Package

maven io.quarkus:quarkus-cache (Maven)

Affected versions

>= 3.3.0.CR1, < 3.5.2
>= 3.2.0.CR1, < 3.2.9.Final

Patched versions

3.5.2
3.2.9.Final

Description

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.

References

Published by the National Vulnerability Database Dec 6, 2023
Published to the GitHub Advisory Database Dec 6, 2023
Reviewed Dec 6, 2023
Last updated Aug 2, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.063%
(29th percentile)

Weaknesses

CVE ID

CVE-2023-6393

GHSA ID

GHSA-xfv5-jqgp-vqhj

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.