dbcve.org
Couchbase ServerApplication · Couchbase

CVE-2022-32192

HIGH · 7.5 CVSS v3.1 Published 2022-06-13
Fix available
A fix is available. Upgrade to 7.0.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Couchbase Server 5.x through 7.x before 7.0.4 exposes Sensitive Information to an Unauthorized Actor.

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 confidence

Couchbase Server versions 5.x through 7.x prior to 7.0.4 contains a vulnerability that allows unauthorized actors to access sensitive information. The specific attack vector and nature of the exposed data are not detailed in the available description, but the issue is classified as high severity (CVSS 7.5).

MitigationUpgrade Couchbase Server to version 7.0.4 or later to remediate this vulnerability. As this is an information disclosure issue, post-upgrade review of access logs and user accounts is recommended.

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
Couchbase ServerApplication
Affected:>= 5.0.0, < 7.0.4

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Couchbase Server version
    Run the following command via Couchbase CLI or inspect the version through the admin console: `couchbase-cli server-info -c localhost -u admin -p password` or check the About page in the Couchbase Web Admin UI
    Affected if The displayed version is >= 5.0.0 and < 7.0.4
  2. Verify network exposure of Couchbase ports
    Check which network interfaces Couchbase is bound to. Review server firewall rules and Couchbase configuration files (typically in /opt/couchbase/etc/couchbase.conf) for the 'bind_address' setting
    Affected if Couchbase is listening on a public or unrestricted IP address (0.0.0.0) rather than localhost or internal-only interfaces, making it externally accessible
  3. Review cluster security settings
    Access Couchbase Web Admin UI under Security > Settings and verify whether authentication is enforced and external network access controls are configured
    Affected if Anonymous or guest access is enabled, or no IP whitelisting/restriction is configured for cluster access
  4. Inspect audit logs for unauthorized access
    Check Couchbase audit logs (located in /opt/couchbase/var/lib/couchbase/logs/audit.log) for any suspicious read operations on sensitive buckets or system metadata from unexpected sources
    Affected if Audit logs show unauthorized read operations on sensitive data from unauthenticated or unauthorized users

You are affected if your Couchbase Server version is between 5.0.0 and 7.0.3 (exclusive of 7.0.4) and the instance is network-accessible to untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.0.4 or later
Fixed in 7.0.4
Interim mitigation

Upgrade Couchbase Server to version 7.0.4 or later to remediate this vulnerability. As this is an information disclosure issue, post-upgrade review of access logs and user accounts is recommended.

Recommended fix High confidence

7.0.4 or later

  1. 1. Back up your Couchbase Server cluster data and configuration
  2. 2. Review Couchbase Server 7.0.4 release notes for any migration requirements
  3. 3. Plan a maintenance window for the upgrade
  4. 4. For rolling upgrades, follow Couchbase's rolling upgrade procedure: upgrade one node at a time, rebalance after each node
  5. 5. After upgrading all nodes, verify all services are operational
  6. 6. Test application connectivity and functionality
Caveat Major version upgrades (5.x/6.x to 7.x) may include feature changes; review 7.0 release notes for migration considerations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Couchbase Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-32192 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-32192 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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