CVE-2021-35943
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 · uneditedCouchbase Server 6.5.x and 6.6.x through 6.6.2 has Incorrect Access Control. Externally managed users are not prevented from using an empty password, per RFC4513.
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 · moderate confidenceCouchbase Server 6.5.x through 6.6.2 contains an incorrect access control vulnerability where externally managed users (such as LDAP/Active Directory users) are not prevented from authenticating with empty passwords, contrary to RFC4513 authentication requirements. This allows unauthorized access to the database without proper credential validation.
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>= 6.5.0, <= 6.5.2>= 6.6.0, < 6.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify installed Couchbase Server versionUse the Couchbase CLI tool (couchbase-cli) or check the product UI to retrieve the exact version number of the installed Couchbase ServerAffected if The version falls within 6.5.0 to 6.5.2 or 6.6.0 to 6.6.2
-
Determine if external authentication is enabledCheck the Couchbase Server authentication settings to see if LDAP or Active Directory integration is configured as an external authentication sourceAffected if External user authentication (LDAP/AD) is enabled and in use
-
Verify authentication configuration for empty passwordsInspect the Couchbase Server authentication configuration files or settings to determine whether the system allows authentication with empty passwords for externally managed usersAffected if The configuration permits empty password authentication for externally managed users
Your environment is affected if Couchbase Server version is 6.5.0-6.5.2 or 6.6.0-6.6.2 AND external LDAP/AD authentication is enabled AND empty password authentication is permitted for those external users.
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 · scoped6.6.3
Upgrade Couchbase Server to a version that addresses this vulnerability and enforce password complexity policies for externally managed users. Additionally, configure the authentication backend to reject empty passwords according to RFC4513.
Couchbase Server 6.6.3 or later (for 6.6.x users); Couchbase Server 6.5.3 or later if available (for 6.5.x users)
- 1. Back up your Couchbase Server configuration and data before upgrading.
- 2. Download Couchbase Server version 6.6.3 or later from the official Couchbase downloads page (www.couchbase.com/downloads).
- 3. Plan your upgrade approach: for production environments, use the rolling upgrade procedure or offline upgrade as appropriate for your cluster configuration.
- 4. For clusters with external authentication (LDAP/Active Directory), verify that empty passwords are no longer accepted after the upgrade by testing user authentication.
- 5. After upgrade, confirm that externally managed users must provide a valid non-empty password per RFC4513 requirements.
- 6. Review user authentication logs to ensure the vulnerability is remediated.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-35943 — 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-2021-35943 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