CVE-2020-9039
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 4.0.0, 4.1.0, 4.1.1, 4.5.0, 4.5.1, 4.6.0 through 4.6.5, 5.0.0, 5.1.1, 5.5.0 and 5.5.1 have Insecure Permissions for the projector and indexer REST endpoints (they allow unauthenticated access).The /settings REST endpoint exposed by the projector process is an endpoint that administrators can use for various tasks such as updating configuration and collecting performance profiles. The endpoint was unauthenticated and has been updated to only allow authenticated users to access these administrative APIs.
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 confidenceThe projector and indexer REST endpoints in Couchbase Server allowed unauthenticated access, enabling remote attackers to access the /settings endpoint for modifying configuration and collecting performance profiles without any authentication. This authentication bypass affects multiple major versions and is rated critical due to the administrative nature of the exposed APIs.
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>= 4.6.0, <= 4.6.5= 4.0.0= 4.1.0= 4.1.1= 4.5.0= 4.5.1= 5.0.0= 5.1.1= 5.5.0= 5.5.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Couchbase Server versionRun 'couchbase-cli server-info -c localhost -u <admin> -p <password>' or check the Couchbase Web Console under Settings > About to determine the installed version numberAffected if The installed version matches one of: 4.0.0, 4.1.0, 4.1.1, 4.5.0, 4.5.1, any version 4.6.0 through 4.6.5, 5.0.0, 5.1.1, 5.5.0, or 5.5.1
-
Test projector endpoint unauthenticated accessSend an HTTP GET request to http://<server>:8092/settings without providing any authentication credentialsAffected if The request returns an HTTP 200 response with configuration data instead of a 401 Unauthorized or 403 Forbidden error
-
Test indexer endpoint unauthenticated accessSend an HTTP GET request to http://<server>:8091/settings without providing any authentication credentialsAffected if The request returns an HTTP 200 response with configuration data instead of a 401 Unauthorized or 403 Forbidden error
-
Verify authentication is required for REST APIsAttempt to access the Couchbase REST API endpoints at ports 8091 (indexer) and 8092 (projector) using curl or a similar tool with no credentials, and observe the responseAffected if Any administrative or configuration endpoint responds with 200 OK and exposes data without requiring authentication
If the Couchbase Server version falls within the affected list and any of the projector (port 8092) or indexer (port 8091) REST endpoints are accessible without authentication, the environment is vulnerable to CVE-2020-9039.
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 · scopedUpgrade to a patched version of Couchbase Server that enforces authentication on the projector and indexer REST endpoints, or apply vendor-supplied patches if available for the affected versions.
Couchbase Server 6.0.0 or later (latest stable 6.x/7.x release)
- Identify your current Couchbase Server version using the Couchbase Web Console or cbversion utility
- Plan for upgrade following Couchbase upgrade documentation (https://docs.couchbase.com/)
- Back up all cluster data and configuration before initiating upgrade
- For production environments, perform a rolling upgrade to maintain availability
- Ensure the target version is compatible with your existing applications and scripts that interact with REST endpoints
- After upgrade, verify that the projector and indexer REST endpoints now require authentication
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9039 — 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-2020-9039 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