# CVE-2025-24858: Information disclosure in Enterprise

> An attacker with network access can obtain the hashed password of the system user from a Develocity server, potentially aiding brute-force attacks.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jan 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-5mvq-pxfx-vffx

## What is CVE-2025-24858?

CVE-2025-24858 is a high-severity vulnerability in Gradle Enterprise, published on 26 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Develocity (formerly Gradle Enterprise) before 2024.3.1 allows an attacker who has network access to a Develocity server to obtain the hashed password of the system user. The hash algorithm used by Develocity was chosen according to best practices for password storage and provides some protection against brute-force attempts. The applicable severity of this vulnerability depends on whether a Develocity server is accessible by external or unauthorized users, and the complexity of the System User password.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

## Which versions are affected by CVE-2025-24858?


## How do I fix CVE-2025-24858?

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

## Is CVE-2025-24858 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24858 and fix it if it is affected.

What it is: CVE-2025-24858 is a high-severity vulnerability in Gradle Enterprise, published on 26 Jan 2025. 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-2025-24858 in the wild and no public exploit code.

Affected product: Gradle Enterprise. 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-2025-24858/ (Markdown: https://insights.sbomify.com/CVE-2025-24858/index.md)
```

## Sources

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

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