CVE-2023-43768
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 · uneditedAn issue was discovered in Couchbase Server 6.6.x through 7.2.0, before 7.1.5 and 7.2.1. Unauthenticated users may cause memcached to run out of memory via large commands.
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 confidenceUnauthenticated users can send large commands to the memcached service embedded in Couchbase Server versions 6.6.x through 7.2.0 (before 7.1.5/7.2.1), causing memory exhaustion and denial of service.
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>= 6.6.0, < 7.1.5= 7.2.0CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Couchbase Server versionRun 'couchbase-cli server-info' or check /opt/couchbase/VERSION.txt to determine the installed versionAffected if Version is >= 6.6.0 and < 7.1.5, or equals 7.2.0
-
Verify memcached service is runningCheck if memcached process is active using 'ps aux | grep memcached' or by querying the Couchbase admin interface for the embedded memcached service statusAffected if The embedded memcached service is running (this is default in Couchbase Server)
-
Confirm memcached network exposureRun 'netstat -tlnp | grep -E "112(10|11)"' or 'ss -tlnp | grep -E "112(10|11)"' to check if memcached ports 11210/11211 are listening on network interfacesAffected if Memcached ports are bound to non-localhost addresses (0.0.0.0 or external IP) rather than 127.0.0.1 only
User is affected if Couchbase Server version is 6.6.0 through 7.2.0 (specifically < 7.1.5 or = 7.2.0) AND the embedded memcached service is network-accessible from untrusted sources.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.1.5
Upgrade to Couchbase Server 7.1.5, 7.2.1, or later. Additionally, restrict network access to memcached ports from untrusted sources as a defense-in-depth measure.
7.1.5 (for 6.6.x-7.0.x) or 7.2.1 (for 7.2.0)
- Identify the current Couchbase Server version using 'couchbase-cli server-info' or the web console
- If running 6.6.x through 7.0.x, plan to upgrade to version 7.1.5
- If running exactly 7.2.0, plan to upgrade to version 7.2.1
- Before upgrading, perform a full backup of all bucket data using 'cbbackup' or through the web console
- Follow the standard Couchbase Server upgrade procedure: stop the server, install the new version, and restart
- After upgrade, verify the memcached process is running correctly and the server responds normally
- Confirm the fix is applied by checking the server version reports 7.1.5 or 7.2.1
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43768 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-43768 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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