dbcve.org
Build Of QuarkusApplication · Redhat

CVE-2023-6393

MEDIUM · 5.3 CVSS v3.1 Published 2023-12-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A context leakage vulnerability in Quarkus Cache Runtime where @CacheResult annotated Uni responses reuse the original completion context from when they were cached. When a subsequent request triggers the cached Uni, it returns using the initial user's context instead of the current request's context, causing sensitive user-specific data to be returned to the wrong requester.

MitigationAvoid using @CacheResult on endpoints that return user-specific or sensitive data; await an official Quarkus framework patch that ensures cached Uni responses are evaluated in the request context rather than the original completion context.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Build Of QuarkusApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Quarkus installation
    Check your project for Quarkus dependencies in pom.xml, build.gradle, or the application's lib directory. Look for io.quarkus:quarkus-core or any quarkus-* packages.
    Affected if Quarkus is present in the environment
  2. Verify Cache extension is enabled
    Search for 'quarkus-cache' in your project dependencies (pom.xml, build.gradle) or check for cache-related configuration in application.properties/application.yaml (quarkus.cache.*).
    Affected if The Quarkus cache extension is included or configured
  3. Locate @CacheResult usage
    Search source code for '@CacheResult' annotations. This can be done with: grep -r '@CacheResult' src/ or find . -name '*.java' -exec grep -l '@CacheResult' {} \;
    Affected if @CacheResult annotations are present in the codebase
  4. Identify cached endpoint return types
    For each @CacheResult location found, examine the method signature and return type. Look for Uni<T> return types and identify what data type T represents.
    Affected if Any @CacheResult method returns a Uni containing user-specific, personalized, or sensitive data (such as user profiles, account details, orders, personal preferences)
  5. Check request context handling
    Review the cached methods to determine if they access context-dependent data such as SecurityIdentity, HttpSession, cookies, request parameters, or any data derived from the current HTTP request context.
    Affected if Cached methods access or return data that should be request-scoped rather than globally shared

You are affected if your Quarkus application uses the cache extension with @CacheResult on endpoints that return Uni responses containing user-specific or context-dependent data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Avoid using @CacheResult on endpoints that return user-specific or sensitive data; await an official Quarkus framework patch that ensures cached Uni responses are evaluated in the request context rather than the original completion context.

Fix this in Build Of Quarkus Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,608.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-6393 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-6393 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data