CVE-2024-46881
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDevelocity (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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceDevelocity's schema migration from version 8 to versions 9/10 fails to include the projects section of the configuration, causing all project settings to reset to defaults. Since projects.enabled defaults to false, project-level access control gets disabled during upgrade, allowing previously restricted project information to be disclosed.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check the installed Develocity versionAccess the Develocity administration UI or check the version via the Develocity API/CLI tool. Look for the version number in the system information or about page.Affected if The installed version is 2024.1.7 or earlier, AND the system was previously at version 2023.3.X or 2023.4.X before the upgrade.
-
Verify the projects section exists in the configurationInspect the Develocity configuration file (typically in the conf directory or via the admin UI configuration viewer). Look for a 'projects' section with an 'enabled' setting.Affected if The projects section is missing or does not contain the enabled setting, indicating the migration failed to preserve project configuration.
-
Check the projects.enabled setting valueIn the configuration, locate projects.enabled under the projects section. Verify whether it is explicitly set to true or is absent/reset to false.Affected if projects.enabled is absent, missing, or set to false (the default), which means project-level access control is disabled.
-
Confirm project-level access control settings are in placeReview the project access control settings in the Develocity admin UI under Projects or Access Control. Check if project-specific permissions, visibility rules, or restricted project data configurations exist.Affected if Project-level access control settings are absent or reverted to default public visibility, meaning restricted project information may be exposed.
A user is affected if they upgraded from Develocity 2023.3.X or 2023.4.X to version 2024.1.0 through 2024.1.7 and the projects.enabled setting is now absent or set to false, causing project access controls to be disabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to Develocity 2024.1.8 or later. After upgrading from affected versions (2023.3.X or 2023.4.X to 2024.1.X up to 2024.1.7), verify that project-level access control settings are correctly configured and not left at default values.
Develocity 2024.1.8 or later
- Upgrade Develocity to version 2024.1.8 or later to remediate the schema migration vulnerability
- After upgrading, verify that Project-level access control is still properly configured in the Enterprise Config
- Confirm that projects.enabled is set to true if project access control was previously enabled
- Review audit logs to check for any unauthorized project access that may have occurred during the vulnerable period
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46881 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-46881 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data