CVE-2022-32564
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 before 7.0.4. In couchbase-cli, server-eshell leaks the Cluster Manager cookie.
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 confidenceAn information disclosure vulnerability in Couchbase Server's couchbase-cli tool allows server-eshell to leak the Cluster Manager authentication cookie. An attacker who obtains this cookie could potentially impersonate an administrator and gain unauthorized access to cluster management functions.
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.0.4CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Identify Couchbase Server installation and versionRun 'couchbase-cli --version' or check the installed package version using your system's package manager (dpkg, rpm, brew, etc.)Affected if The installed version is below 7.0.4 (e.g., 7.0.3, 7.0.2, 6.6.x, etc.)
-
Check for couchbase-cli usage with server-eshellReview any scripts, automation, or documentation that invoke 'couchbase-cli server-eshell' commandAffected if The server-eshell component of couchbase-cli is being used to interact with the Cluster Manager
-
Inspect CLI command outputs for credential leakageExamine terminal outputs, log files, or shell history where couchbase-cli commands have been executed, looking for authentication cookie or session token stringsAffected if Authentication cookies or session tokens appear in plain text in any output or log files associated with couchbase-cli operations
-
Verify cluster manager accessibilityCheck network exposure of Couchbase Cluster Manager ports (8091, 18091, etc.) and review access logs for unauthorized session reuseAffected if The Cluster Manager is network-accessible and there are signs of session cookie reuse from potentially leaked credentials
You are affected if Couchbase Server version is below 7.0.4 AND the couchbase-cli server-eshell component is in use, as this combination enables the authentication cookie disclosure.
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 · scoped7.0.4
Upgrade Couchbase Server to version 7.0.4 or later to obtain the patch. If immediate upgrading is not feasible, avoid using the server-eshell component and ensure no unauthorized parties can observe CLI command outputs containing sensitive session data.
7.0.4
- 1. Back up all Couchbase Server data and cluster configuration before starting the upgrade.
- 2. Review the official Couchbase Server 7.0.4 release notes for any migration requirements or known issues.
- 3. Plan a maintenance window as the upgrade will require cluster downtime.
- 4. Perform a rolling upgrade or offline upgrade following Couchbase documentation, upgrading to version 7.0.4 or later.
- 5. After upgrade, verify the cluster is functioning correctly and the couchbase-cli commands work as expected.
- 6. Verify that server-eshell no longer leaks the Cluster Manager cookie by testing couchbase-cli operations.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32564 — 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-2022-32564 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