# CVE-2022-25364: Misconfiguration in n/a

> Default anonymous write access in Gradle Enterprise build cache allows attackers to inject malicious code executed during builds.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-rqrc-wvq6-vxfv

## What is CVE-2022-25364?

CVE-2022-25364 is a high-severity vulnerability in n/a, published on 17 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Gradle Enterprise before 2021.4.2, the default built-in build cache configuration allowed anonymous write access. If this was not manually changed, a malicious actor with network access to the build cache could potentially populate it with manipulated entries that execute malicious code as part of a build. As of 2021.4.2, the built-in build cache is inaccessible-by-default, requiring explicit configuration of its access-control settings before it can be used. (Remote build cache nodes are unaffected as they are inaccessible-by-default.)

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2022-25364?

It affects 1 product.


Products: Gradle Enterprise.

## How do I fix CVE-2022-25364?

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

## Is CVE-2022-25364 being exploited?

There is no known exploitation of CVE-2022-25364 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-41575](https://insights.sbomify.com/CVE-2022-41575/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25364 and fix it if it is affected.

What it is: CVE-2022-25364 is a high-severity vulnerability in n/a, published on 17 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-25364 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-2022-25364/ (Markdown: https://insights.sbomify.com/CVE-2022-25364/index.md)
```

## Sources

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

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