dbcve.org
Couchbase ServerApplication · Couchbase

CVE-2021-37842

HIGH · 7.5 CVSS v3.1 Published 2021-11-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
metakv in Couchbase Server 7.0.0 uses Cleartext for Storage of Sensitive Information. Remote Cluster XDCR credentials can get leaked in debug logs. Config key tombstone purging was added in Couchbase Server 7.0.0. This issue happens when a config key, which is being logged, has a tombstone purger time-stamp attached to it.

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 confidence

The metakv component in Couchbase Server 7.0.0 stores sensitive information in cleartext, specifically exposing Remote Cluster XDCR (Cross Data Center Replication) credentials in debug logs. This occurs because when a config key with a tombstone purger timestamp is logged, the credential data gets included in the log output.

MitigationOrganizations should upgrade to a patched version of Couchbase Server 7.0.0 that addresses this cleartext credential logging issue, and immediately audit existing debug logs for potential credential exposure.

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:= 7.0.0= 7.0.1

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 Couchbase Server version
    Run 'cbverinfo' or check the Couchbase Server admin UI (Settings > About) to determine the exact installed version
    Affected if Version is 7.0.0 or 7.0.1 exactly
  2. Verify XDCR configuration exists
    Navigate to Couchbase Server Admin UI > XDCR or run 'cbacl -cluster' to list remote clusters. XDCR credentials are stored when you configure a remote cluster for cross-datacenter replication
    Affected if One or more remote clusters are configured for XDCR with stored credentials
  3. Confirm debug logging is enabled
    Check the log configuration in Couchbase Server admin UI > Settings > Log Settings, or inspect the default.log.conf file in the Couchbase installation directory under /etc/couchbase/logging
    Affected if Debug or trace-level logging is enabled for metakv or general component logs
  4. Search debug logs for credential exposure
    Search debug log files (typically in /opt/couchbase/var/lib/couchbase/logs/) for patterns matching 'xdcr' and credential-like strings such as 'password', 'credentials', or base64-encoded values in entries related to metakv or tombstone purger
    Affected if Debug logs contain cleartext XDCR credentials or password data in metakv or config-related entries

You are affected if you run Couchbase Server 7.0.0 or 7.0.1 with XDCR configured and debug logging enabled, and your debug logs may contain exposed credentials from the metakv tombstone purger logging issue

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Organizations should upgrade to a patched version of Couchbase Server 7.0.0 that addresses this cleartext credential logging issue, and immediately audit existing debug logs for potential credential exposure.

Recommended fix Moderate confidence

Couchbase Server 7.0.2 or later stable release

  1. 1. Identify all Couchbase Server 7.0.0 and 7.0.1 instances in the environment
  2. 2. Review current debug logging configurations and ensure no XDCR credentials are currently exposed in logs
  3. 3. Plan for upgrade to a fixed release version (7.0.2 or later)
  4. 4. Before upgrading, take full backups of all buckets and cluster configuration
  5. 5. Schedule maintenance window for upgrade procedure
  6. 6. Perform upgrade following Couchbase Server upgrade documentation
  7. 7. After upgrade, verify that debug logs no longer contain XDCR credential information
  8. 8. Audit existing logs for any potential credential exposure and rotate compromised credentials
Caveat Review Couchbase 7.0.2 release notes for any configuration or feature changes that may affect existing applications

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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