# 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.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Nov 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-p62q-5483-h57v

## 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 (Cleartext Storage of Sensitive Information in an Environment Variable)

## 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 | Ecosystem | 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: 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](https://insights.sbomify.com/CVE-2022-4116/): Code injection in quarkus dev ui config editor (critical 9.8)
- [CVE-2022-2466](https://insights.sbomify.com/CVE-2022-2466/): Quarkus does not terminate HTTP requests header context (critical 9.8)
- [CVE-2024-12225](https://insights.sbomify.com/CVE-2024-12225/): Io.quarkus:quarkus-security-webauthn: quarkus webauthn unexpected authentication bypass (critical 9.1)
- [CVE-2026-39852](https://insights.sbomify.com/CVE-2026-39852/): Quarkus authorization bypass via semicolon path normalization inconsistency (high 8.8)
- [CVE-2022-0981](https://insights.sbomify.com/CVE-2022-0981/): Privilege escalation in quarkus (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-5720 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2023-5720 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.quarkus:quarkus-project (Maven): affected from 3.0.0.CR1 up to 3.5.1; no fix listed
- io.quarkus:quarkus-project (Maven): affected from 3.0.0.CR1 up to 3.5.1; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-5720/ (Markdown: https://insights.sbomify.com/CVE-2023-5720/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-5720
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-5720
- OSV: https://osv.dev/vulnerability/CVE-2023-5720

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-5720/
Summaries are generated and may contain mistakes; the official description above is the record.