dbcve.org
Couchbase ServerApplication · Couchbase

CVE-2023-49931

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-29
Fix available
A fix is available. Upgrade to 7.2.4 or later.
See remediation →
100/100
Remediation priority · Urgent
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.2.4. SQL++ cURL calls to /diag/eval are not sufficiently restricted.

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 before 7.2.4 does not properly restrict access to the /diag/eval endpoint, which allows SQL++ queries to be executed via cURL. This unrestricted endpoint can be exploited for unauthorized data access or potentially remote code execution.

MitigationUpgrade Couchbase Server to version 7.2.4 or later. Alternatively, restrict network access to the /diag/eval endpoint via firewall rules or authentication controls until patching is possible.

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.2.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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 'cb_version' command from the Couchbase tools directory, or query the cluster via the admin API at http://<host>:8091/pools/default with appropriate credentials, or check the product version in the server'sAbout dialog in the admin UI
    Affected if Installed version is 7.2.4 or higher (not affected). If version is 7.2.3 or below but 5.0.0 or above, the system falls within the affected range.
  2. Verify admin port binding
    Check the configuration setting for the admin HTTP service in the Couchbase config file (typically in /opt/couchbase/var/lib/couchbase/config or via the UI under Settings > Advanced > 'Node to Node Encryption' or 'External Statistics' settings). Look for the network interface binding
    Affected if The admin port (default 8091) is bound to 0.0.0.0 or an IP accessible from untrusted networks, meaning the endpoint could be reached externally.
  3. Test /diag/eval endpoint accessibility
    Send an unauthenticated HTTP request to http://<couchbase-host>:8091/diag/eval using curl. For example: curl -v http://localhost:8091/diag/eval. A valid response (even an error) rather than an authentication challenge indicates the endpoint is reachable
    Affected if The endpoint responds without requiring authentication credentials, indicating unrestricted access.
  4. Confirm authentication is enforced on the endpoint
    Send the same curl request with invalid credentials or no credentials. Check whether the response includes an authentication prompt, HTTP 401, or redirects to a login page rather than executing the request
    Affected if The endpoint executes the request or returns diagnostic information without prompting for login, confirming it is unprotected.

You are affected if your Couchbase Server version is 7.2.3 or below (but 5.0.0 or above) AND the /diag/eval endpoint is accessible without authentication on an exposed network interface.

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.2.4 or later
Fixed in 7.2.4
Interim mitigation

Upgrade Couchbase Server to version 7.2.4 or later. Alternatively, restrict network access to the /diag/eval endpoint via firewall rules or authentication controls until patching is possible.

Recommended fix High confidence

7.2.4

  1. Download Couchbase Server version 7.2.4 or later from the official Couchbase download portal
  2. Review Couchbase upgrade documentation for your current version to ensure a compatible upgrade path
  3. Back up all data and cluster configuration before initiating the upgrade
  4. Perform the upgrade following standard Couchbase Server upgrade procedures
  5. After upgrade, verify that the /diag/eval endpoint access controls are properly enforced

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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