CVE-2024-56178
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 · uneditedAn issue was discovered in Couchbase Server 7.6.x through 7.6.3. A user with the security_admin_local role can create a new user in a group that has the admin role.
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 confidenceA privilege escalation vulnerability in Couchbase Server 7.6.x through 7.6.3 allows a user with the security_admin_local role to create new users and assign them to groups that have the admin role, effectively bypassing intended role boundaries and granting full administrative privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 7.6.0, <= 7.6.3CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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.
-
Determine Couchbase Server versionRun 'cbversion' command or check via REST API at http://<host>:8091/pools/default or inspect the installation directory for version file. Alternatively, log into Couchbase Web UI and navigate to About page.Affected if Installed version is greater than or equal to 7.6.0 and less than or equal to 7.6.3
-
Identify users with security_admin_local roleAccess Couchbase Web UI, go to Security > Users. Look for users listed with the security_admin_local role in the Role column. Alternatively, query via REST API: GET http://<host>:8091/settings/rbac/usersAffected if Any user account has the security_admin_local role assigned
-
Check for groups with admin roleIn Couchbase Web UI, navigate to Security > Groups. Review each group and verify if the admin role is assigned. Alternatively, query groups via REST API: GET http://<host>:8091/settings/rbac/groupsAffected if Any group exists with the admin role enabled
-
Review user-to-group assignmentsIn Couchbase Web UI under Security > Users, examine which groups each user belongs to. Specifically check if any user with security_admin_local role is assigned to a group that contains the admin role.Affected if A user with security_admin_local role is assigned to a group that has admin role privileges
You are affected if your Couchbase Server version is between 7.6.0 and 7.6.3 inclusive AND you have users with the security_admin_local role assigned to groups containing the admin role.
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 Couchbase Server to version 7.6.4 or later to receive the security patch that enforces proper role-based access control boundaries for the security_admin_local role.
Couchbase Server 7.6.4 or later (recommended: latest stable 7.6.x release)
- 1. Back up the Couchbase Server cluster configuration and data before upgrading.
- 2. Ensure no critical operations are running on the cluster.
- 3. Download Couchbase Server version 7.6.4 or later from the official Couchbase downloads page.
- 4. Perform a rolling upgrade or planned downtime upgrade following Couchbase's upgrade documentation.
- 5. After upgrade, verify that the security_admin_local role can no longer create users with admin privileges.
- 6. Review user/group assignments to ensure proper role configuration.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-56178 — 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-56178 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