CVE-2025-24858
First published: Sun Jan 26 2025(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Develocity | <2024.3.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2025-24858?
CVE-2025-24858 has a moderate severity rating due to the potential for unauthorized access to hashed passwords.
How do I fix CVE-2025-24858?
To fix CVE-2025-24858, upgrade Develocity to version 2024.3.1 or later.
Who is affected by CVE-2025-24858?
CVE-2025-24858 affects users of Develocity versions prior to 2024.3.1.
What type of data can be compromised with CVE-2025-24858?
CVE-2025-24858 allows an attacker to obtain the hashed password of the system user.
Is the password hash used in CVE-2025-24858 secure?
The hash algorithm used in CVE-2025-24858 follows best practices for password storage, but it still presents a risk if exposed.
- agent/references
- agent/type
- agent/description
- agent/first-publish-date
- agent/author
- collector/nvd-api
- source/NVD
- agent/severity
- agent/last-modified-date
- agent/weakness
- agent/source
- agent/softwarecombine
- agent/tags
- collector/mitre-cve
- source/MITRE
- collector/epss-latest
- source/FIRST
- agent/epss
- agent/event
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/gradle
- canonical/develocity