CVE-2023-5720 Quarkus: build env information disclosure via gradle plugin
Attackers can access sensitive build system information from Quarkus applications due to unsanitized artifacts created by the Gradle plugin.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2023-5720?
CVE-2023-5720 is a high-severity vulnerability in gradle-plugin, published on 15 Nov 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
A 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.
Weakness: CWE-526
Which versions are affected by CVE-2023-5720?
2 open source packages ship an affected version, including io.quarkus:quarkus-project. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
io.quarkus:quarkus-project Maven | From 3.0.0.CR1 to 3.5.1 | None |
io.quarkus:quarkus-project Maven | From 3.0.0.CR1 to 3.5.1 | None |
Products include Quarkus Quarkus.
How do I fix CVE-2023-5720?
No fix has been published for CVE-2023-5720 yet. Limit exposure of the affected software until one is available.
Is CVE-2023-5720 being exploited?
There is no known exploitation of CVE-2023-5720 in the wild and no public exploit code.
Other vulnerabilities in gradle-plugin
- CVE-2022-4116 Code injection in quarkus dev ui config editor
- CVE-2022-2466 Quarkus does not terminate HTTP requests header context
- CVE-2024-12225 Io.quarkus:quarkus-security-webauthn: quarkus webauthn unexpected authentication bypass
- CVE-2026-39852 Quarkus authorization bypass via semicolon path normalization inconsistency
- CVE-2022-0981 Privilege escalation in quarkus
Sources
Also known as GHSA-p62q-5483-h57v.