CVE-2023-5720
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 · uneditedA flaw was found in Quarkus, where it does not properly sanitize artifacts created using the Gradle plugin, allowing certain build system information to remain. This flaw allows an attacker to access potentially sensitive information from the build system within the application.
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 · high confidenceQuarkus fails to properly sanitize build artifacts generated by its Gradle plugin, leaving build system metadata and potentially sensitive information embedded in the application. An attacker who gains access to the compiled artifacts or build outputs can extract this exposed build system information.
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>= 3.0.1, < 3.2.8= 3.0.0CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify your Quarkus versionCheck the gradle.properties file or build.gradle/build.gradle.kts for the Quarkus version property (quarkus.platform.version or the Quarkus dependency version)Affected if The version is 3.0.0 or falls between 3.0.1 and 3.2.7 inclusive
-
Confirm Gradle is the build toolVerify that your project uses build.gradle or build.gradle.kts (not Maven pom.xml) for buildingAffected if Gradle is used as the build system
-
Inspect Gradle build metadata in outputsExamine the contents of the built application JAR (or other output artifact) for .gradle directory files, gradle-wrapper.properties, or other Gradle-specific metadata filesAffected if Gradle build system metadata files are present inside the compiled application artifacts
-
Check for embedded build configurationSearch the build output directory (typically build/ or target/) for files containing build system paths, usernames, or repository configurations that should not be included in production artifactsAffected if Build system paths, credentials, or repository URLs are embedded in the compiled artifacts
You are affected if your Quarkus version is 3.0.0 or between 3.0.1 and 3.2.7 AND you use Gradle to build, with Gradle metadata or build system information present inside your compiled application artifacts.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped3.2.8
Update Quarkus to the patched version that properly sanitizes Gradle build artifacts, and audit existing built artifacts for any exposed sensitive build system information.
Quarkus 3.2.8 or later (latest 3.x stable release)
- Identify all Quarkus applications using Gradle that are on versions 3.0.0 or >= 3.0.1 and < 3.2.8
- Upgrade Quarkus to version 3.2.8 or later (e.g., 3.2.8, 3.3.0, or latest stable 3.x)
- Update the quarkus-gradle-plugin dependency version in build.gradle or build.gradle.kts to match the upgraded Quarkus version
- Clean and rebuild the application using Gradle to regenerate sanitized artifacts
- Verify the fix by inspecting the built artifacts to confirm no build system information (e.g., Gradle user home path, version details) is exposed in the final WAR/JAR
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5720 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-5720 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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