Security readout for executives and security teams
Plain-English summary
A Quarkus caching flaw can return one user's sensitive response to another user when an application caches a Uni with @CacheResult and reuses the original completion context. The issue affects confidentiality, not integrity or availability, and requires a specific application pattern.
Executive priority
Treat this as a targeted confidentiality risk. Prioritize internet-facing or multi-user services that cache personalized Uni responses. Urgency is moderate because exploitation depends on a specific design and high complexity, but exposed data could be highly sensitive. Escalate affected applications for prompt review and vendor-guided remediation.
Technical view
CVE-2023-6393 is a CWE-200 exposure in Quarkus Cache Runtime. A cached Uni may retain its initial completion context, causing later request processing to switch from the current request context. Under the described POST scenario, a low-privileged remote user could receive data intended for another user. CVSS 3.1 is 5.3, with high attack complexity.
Likely exposure
Exposure is limited to affected Red Hat Quarkus applications using quarkus-cache, @CacheResult, and cached Uni values that retain sensitive request context. The bundle identifies 2.13.9.Final-redhat-00002 and Red Hat build of Quarkus 3, but provides no complete affected-version range.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the bundle. Exploitation requires low privileges, no user interaction, network access, and a particular caching and context-reuse condition. Successful abuse could disclose another user's sensitive response.
Researcher notes
The weakness is CWE-200 and affects confidentiality only under the supplied CVSS vector. Key review points are cache-key scope, Uni completion-context retention, and transitions between cached and current request contexts. The bundle does not provide a complete affected-version matrix, fixed versions, proof of exploitation, or a confirmed workaround.
Mitigation direction
- Inventory affected Quarkus applications and their quarkus-cache versions.
- Identify @CacheResult methods returning Uni values and handling user-specific data.
- Review RHSA-2023:7700 and Red Hat guidance for applicable updates.
- Prioritize removing sensitive request context from shared cached results.
- Apply vendor-supported remediation after compatibility testing.
Validation and detection
- Confirm deployed Quarkus and quarkus-cache versions against Red Hat guidance.
- Review cached Uni completion logic for retained authentication or request context.
- Test concurrent authorized sessions for strict response isolation.
- Verify cache keys separate every user-specific or authorization-dependent result.
- Retest isolation after applying vendor-supported remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-6393 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N1.63.6redhatVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineredhat
Reported to Red Hat.
- Source timelineredhat
Made public.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2023:7700CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2023-6393CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2253113CVE reference, redhat · issue-tracking, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Sensitive Information to an Unauthorized Actor
Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.