dbcve.org
Couchbase ServerApplication · Couchbase

CVE-2022-33173

HIGH · 7.5 CVSS v3.1 Published 2022-07-12
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 algorithm-downgrade issue was discovered in Couchbase Server before 7.0.4. Analytics Remote Links may temporarily downgrade to non-TLS connection to determine the TLS port number, using SCRAM-SHA instead.

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

Couchbase Server before 7.0.4 contains an algorithm-downgrade vulnerability in Analytics Remote Links. The system may temporarily downgrade to a non-TLS connection to determine the TLS port number, using SCRAM-SHA authentication instead of properly negotiated TLS, potentially exposing credentials or allowing man-in-the-middle attacks.

MitigationUpgrade Couchbase Server to version 7.0.4 or later to resolve the algorithm downgrade vulnerability in Analytics Remote Links.

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:>= 6.6.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. Verify Couchbase Server version
    Run command: couchbase-cli --version or cbversion to obtain the exact installed version number
    Affected if Installed version is 6.6.0 through 7.0.3 (any version >= 6.6.0 and < 7.0.4)
  2. Confirm Analytics service is enabled
    Check if Analytics node(s) exist in the cluster via Couchbase Web UI under Servers tab, or query cluster analytics state using cbq or REST API
    Affected if Analytics service is active on any node in the cluster
  3. Identify Analytics Remote Links configuration
    Query Analytics settings via REST API (GET /analytics/link) or use cbq tool to run: SELECT * FROM system:links WHERE type = 'couchbase';
    Affected if Any Analytics Remote Links of type 'couchbase' are configured pointing to external clusters
  4. Check for non-TLS link configuration
    Examine the Remote Link settings to see if TLS/encryption is disabled or set to 'none'. Look for link definitions without proper TLS configuration in the Analytics scope
    Affected if Remote Links are configured with TLS disabled or with a configuration that allows fallback to non-TLS authentication
  5. Inspect active Analytics connections
    Monitor network connections or review Analytics diagnostic logs for any SCRAM-SHA authentication occurring over non-TLS ports
    Affected if SCRAM-SHA authentication is observed on plain-text Analytics connections to remote links

User is affected if Couchbase Server version is between 6.6.0 and 7.0.3, Analytics service is enabled, and Analytics Remote Links are configured without proper TLS enforcement.

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 resolve the algorithm downgrade vulnerability in Analytics Remote Links.

Recommended fix High confidence

7.0.4

  1. 1. Create a complete backup of the Couchbase Server data and cluster configuration
  2. 2. Review the Couchbase Server 7.0.4 release notes and upgrade documentation for any pre-upgrade requirements
  3. 3. Ensure all dependent applications and clients are compatible with version 7.0.4
  4. 4. Plan for appropriate maintenance window as cluster will require a brief restart
  5. 5. Perform the upgrade to Couchbase Server version 7.0.4 or later following the standard upgrade procedure
  6. 6. After upgrade, verify that Analytics Remote Links are functioning with TLS enabled
  7. 7. Confirm the vulnerability is remediated by checking that connections no longer fall back to non-TLS SCRAM-SHA authentication
Caveat Couchbase major version upgrades may introduce compatibility changes; review 7.0.4 release notes for any breaking changes from 6.x

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

Fix this in Couchbase Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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