CVE intelligence and bounded remediation

CVE-2024-46881 — Develocity (formerly Gradle Enterprise) before 2024.1.8 has Incorrect Access Control

High CVSS 7.1

Develocity (formerly Gradle Enterprise) before 2024.1.8 has Incorrect Access Control. Project-level access control configuration was introduced in Enterprise Config schema version 8. Migration functionality from schema version 8 to versions 9 and 10 (in affected vulnerable versions) does not include the projects section of the configuration. This leads to all of the project settings being reset to their defaults when the old schema is loaded. In the case of projects.enabled, the default is false. Thus, using an enterprise config v8 results in Project level access control being disabled, even if it was previously enabled, and previously restricted project information disclosed. Most commonly, this occurs when a Develocity instance is upgraded from an earlier version. Specifically, this occurs if: Develocity 2023.3.X is upgraded to 2023.4.X; Develocity 2023.3.X is upgraded to 2024.1.X up to and including 2024.1.7; or Develocity 2023.4.X is upgraded to 2024.1.X up to and including 2024.1.7. The flaw does not occur when upgrading to a fixed version. An upgrade can only be triggered via administrator access, and cannot be forced by an external attacker.

Severity
High
CVSS
7.1 (3.1)
Published
2025-01-26
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-732

Affected products

No browser-safe affected-product rows are available.

Matched remediation archetype

Privilege escalation and unsafe privilege management

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Map service accounts, operating-system identities, roles, capabilities, impersonation, set-user transitions, and administrative helper paths.
  • Determine whether untrusted users or lower-privilege processes can reach the affected transition or modify inputs it trusts.
  • Review file, socket, registry, device, job, container, and cloud-role permissions used before and after privilege changes.

Remediate safely

  • Apply the supported fix and redesign privileged operations as a minimal, authenticated, allowlisted interface.
  • Drop privileges before processing untrusted input, verify the drop succeeds, and remove unnecessary roles, capabilities, and write permissions.
  • Validate ownership and permissions at time of use and add explicit lower-to-higher privilege boundary tests.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.