CVE-2025-24858

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

The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.

Potential Mitigations

• Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
• Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/12.html
• https://cwe.mitre.org/data/definitions/217.html
• https://cwe.mitre.org/data/definitions/612.html
• https://cwe.mitre.org/data/definitions/613.html
• https://cwe.mitre.org/data/definitions/618.html
• https://cwe.mitre.org/data/definitions/619.html
• https://cwe.mitre.org/data/definitions/621.html
• https://cwe.mitre.org/data/definitions/622.html
• https://cwe.mitre.org/data/definitions/623.html

References

• https://security.gradle.com/advisory/2025-01