# CVE-2021-41619: An issue was discovered in Gradle Enterprise before 2021.1.2.


- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8wc9-4crc-jr2q

## What is CVE-2021-41619?

CVE-2021-41619 is a high-severity vulnerability in n/a, published on 27 Oct 2021. 

### Official description

An issue was discovered in Gradle Enterprise before 2021.1.2. There is potential remote code execution via the application startup configuration. The installation configuration user interface (available to administrators) allows specifying arbitrary Java Virtual Machine startup options. Some of these options, such as -XX:OnOutOfMemoryError, allow specifying a command to be run on the host. This can be abused to run arbitrary commands on the host, should an attacker gain administrative access to the application.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2021-41619?

It affects 1 product.


Products: Gradle Enterprise.

## How do I fix CVE-2021-41619?

No fix has been published for CVE-2021-41619 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-41619 being exploited?

There is no known exploitation of CVE-2021-41619 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-49238](https://insights.sbomify.com/CVE-2023-49238/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2022-27919](https://insights.sbomify.com/CVE-2022-27919/): Missing authorization in n/a (critical 9.8)
- [CVE-2019-11402](https://insights.sbomify.com/CVE-2019-11402/): Information disclosure in n/a (critical 9.8)
- [CVE-2020-15776](https://insights.sbomify.com/CVE-2020-15776/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2022-25364](https://insights.sbomify.com/CVE-2022-25364/): Misconfiguration in n/a (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-41619 and fix it if it is affected.

What it is: CVE-2021-41619 is a high-severity vulnerability in n/a, published on 27 Oct 2021. 
Exploitation: There is no known exploitation of CVE-2021-41619 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2021-41619/ (Markdown: https://insights.sbomify.com/CVE-2021-41619/index.md)
```

## Sources

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

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