dbcve.org
Couchbase ServerApplication · Couchbase

CVE-2023-49932

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-29
Fix available
A fix is available. Upgrade to 7.2.4 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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. An attacker can bypass SQL++ N1QL cURL host restrictions.

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 contains a vulnerability where an attacker can bypass SQL++ N1QL cURL host restrictions. This security bypass allows potentially malicious queries to access restricted hosts through the N1QL cURL function, which should normally be limited to permitted endpoints.

MitigationUpgrade Couchbase Server to version 7.2.4 or later to remediate this vulnerability. Verify that N1QL cURL host restrictions are functioning correctly after the upgrade.

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
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/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 installed Couchbase Server version
    Run 'couchbase-cli server-info' or check the Couchbase Web Console Dashboard to view the server version
    Affected if The installed version is lower than 7.2.4 (versions 5.0.0 through 7.2.3 are affected)
  2. Confirm N1QL service is active
    Access the Couchbase Web Console, navigate to Settings > Services, or use the REST API endpoint '/pools/default/services' to verify the N1QL service is running on at least one node
    Affected if N1QL service is enabled and the server version is vulnerable (below 7.2.4)
  3. Verify N1QL cURL function configuration
    Query the system:indexes or use the N1QL EXPLAIN on a sample cURL query to inspect whether the cURL function is operational. Check the cluster settings via Couchbase Web Console under Security or via the REST API '/settings/curlwhitelist'
    Affected if The cURL whitelist/restriction settings are present and the version is below 7.2.4, indicating the bypass vulnerability could be exploited
  4. Review cURL host allowlist configuration
    Access the Couchbase Web Console, navigate to Security > External Services or use the REST API endpoint GET '/settings/curlwhitelist' to inspect the permitted hosts for N1QL cURL queries
    Affected if Host restrictions exist but the server version is below 7.2.4, meaning the bypass flaw may allow access to non-permitted hosts

A user is affected if Couchbase Server version is 5.0.0 through 7.2.3 and the N1QL cURL function is enabled with configured host restrictions.

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 to remediate this vulnerability. Verify that N1QL cURL host restrictions are functioning correctly after the upgrade.

Recommended fix High confidence

7.2.4 or later (latest stable 7.x release)

  1. 1. Back up all Couchbase data and cluster configuration before starting the upgrade.
  2. 2. Review the Couchbase Server upgrade documentation for your current version to ensure compatibility with 7.2.4.
  3. 3. Schedule a maintenance window as upgrades require cluster downtime.
  4. 4. For single-node clusters, stop the Couchbase service, install version 7.2.4 or later, and restart.
  5. 5. For multi-node clusters, follow the rolling upgrade procedure: rebalance out one node, upgrade that node, rebalance back in, and repeat for all nodes.
  6. 6. After upgrade, verify the N1QL cURL function now properly enforces host restrictions by testing with a disallowed host.
  7. 7. Confirm all applications and services are functioning correctly after the upgrade.
Caveat Review release notes for any breaking changes between your current version and 7.2.4; minor version upgrades typically maintain backward compatibility but N1QL query behavior changes may require testing.

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 the upgrade done

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-2023-49932 — 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-49932 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