CVE-2023-36667
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 · uneditedCouchbase Server 7.1.4 before 7.1.5 and 7.2.0 before 7.2.1 allows Directory Traversal.
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 confidenceCouchbase Server versions 7.1.4 before 7.1.5 and 7.2.0 before 7.2.1 contain a directory traversal vulnerability that allows attackers to access files outside the intended directory boundaries using path traversal sequences.
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>= 2.0.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check Couchbase Server versionRun 'couchbase-server --version' or access the administration console and look at the Server Version displayed on the startup page or in About sectionAffected if The installed version is 7.2.0, or is between 2.0.0 and 7.1.4 inclusive (meaning less than 7.1.5)
-
Confirm if web administration interface is accessibleAttempt to reach the Couchbase web administration port (default 8091) from network locations where the server is accessibleAffected if The administration interface is exposed to untrusted networks - directory traversal attacks typically target web-facing components
-
Identify exposed REST API endpointsReview Couchbase Server configuration files in /opt/couchbase/etc/ for exposed API endpoints, particularly any that handle file paths or document attachmentsAffected if File handling or path-based REST API endpoints are enabled and accessible - the directory traversal vulnerability exploits path handling in these endpoints
You are affected if your installed Couchbase Server version is 7.2.0 or falls between 2.0.0 and 7.1.4, and you have web-facing components that handle file paths accessible to attackers.
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 Couchbase Server to version 7.1.5, 7.2.1, or later to resolve the directory traversal vulnerability.
Couchbase Server 7.1.5 or later, or 7.2.1 or later
- 1. Identify the current Couchbase Server version using 'couchbase-cli server-info' or the Couchbase web console
- 2. If running version 7.1.4 or earlier (7.1.x series), upgrade to version 7.1.5 or later
- 3. If running version 7.2.0, upgrade to version 7.2.1 or later
- 4. For versions below 7.1.x, plan an upgrade path to either 7.1.5+ or 7.2.1+ following Couchbase upgrade documentation
- 5. Before upgrading, back up all cluster data and configuration
- 6. Perform the upgrade following the standard Couchbase Server upgrade procedure (rolling upgrade or cluster upgrade depending on infrastructure)
- 7. After upgrade, verify the directory traversal vulnerability is resolved by testing file access controls
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-36667 — 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-36667 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