dbcve.org
Couchbase ServerApplication · Couchbase

CVE-2022-32560

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
An issue was discovered in Couchbase Server before 7.0.4. XDCR lacks role checking when changing internal settings.

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

An authorization bypass vulnerability in Couchbase Server's XDCR (Cross Data Center Replication) component allows users to modify internal settings without proper role checking, potentially enabling unauthorized configuration changes to replication streams.

MitigationUpgrade Couchbase Server to version 7.0.4 or later to receive the patch that enforces proper role-based access control on XDCR settings.

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:>= 4.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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checks

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

  1. Identify Couchbase Server version
    Run 'cbversion' from the Couchbase command line tools or check the version displayed in the Couchbase Web Console under 'Server Nodes' or 'Settings > About'. Compare the installed version against the affected range: 4.0.0 to 7.0.4 (excluding 7.0.4).
    Affected if The installed version is 4.0.0 or higher but lower than 7.0.4.
  2. Confirm XDCR feature is in use
    Access the Couchbase Web Console and navigate to the XDCR section (typically under 'Replications' or 'XDCR'). Check if any replication streams, remote clusters, or XDCR bucket configurations exist.
    Affected if XDCR replications or remote cluster references are defined in the environment.
  3. Verify XDCR settings accessibility
    Attempt to view or modify XDCR settings through the Couchbase Web Console, REST API (e.g., GET /pools/default/remoteClusters), or CLI (e.g., couchbase-cli xdcr-setup). Note whether any user role validation occurs when accessing these settings.
    Affected if Users without the appropriate administrator role can view or modify XDCR configuration parameters.
  4. Check user role assignments for XDCR
    Review user roles in Couchbase Security settings. Determine if users with limited roles (such as 'Replication Admin' or custom roles) can access XDCR internal settings that should require full admin privileges.
    Affected if Non-administrator users have the ability to modify XDCR internal settings without proper authorization checks.

You are affected if Couchbase Server version is 4.0.0 or higher but lower than 7.0.4 AND XDCR replication is configured or in use in your environment.

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 receive the patch that enforces proper role-based access control on XDCR settings.

Recommended fix High confidence

7.0.4 or later (recommended: latest stable 7.x release)

  1. Backup all Couchbase data and cluster configuration before initiating the upgrade
  2. Review Couchbase Server 7.x upgrade documentation for breaking changes and migration requirements
  3. Plan the upgrade path - consider upgrading through intermediate versions if direct jump has compatibility issues
  4. Stop XDCR replications and ensure no active configuration changes during upgrade
  5. Upgrade Couchbase Server to version 7.0.4 or later (recommended: latest stable 7.x release)
  6. After upgrade, verify that role-based access control is properly enforced for XDCR settings
  7. Test XDCR functionality to confirm replication works correctly with the new authorization checks in place
Caveat Major version upgrade from 4.x to 7.x may introduce breaking changes in query syntax, APIs, and features - review Couchbase 7.0 migration guide

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

Fix this in Couchbase Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,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 $8,256.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-32560 — 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-32560 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