CVE-2019-11464
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 · uneditedSome enterprises require that REST API endpoints include security-related headers in REST responses. Headers such as X-Frame-Options and X-Content-Type-Options are generally advisable, however some information security professionals additionally look for X-Permitted-Cross-Domain-Policies and X-XSS-Protection, which are more generally applicable to HTML endpoint, to be included too. These headers were not included in Couchbase Server 5.5.0 and 5.1.2 . They are now included in version 6.0.2 in responses from the Couchbase Server Views REST API (port 8092).
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 5.5.0 and 5.1.2 Views REST API (port 8092) lack several HTTP security headers (X-Frame-Options, X-Content-Type-Options, X-Permitted-Cross-Domain-Policies, X-XSS-Protection) in responses, reducing defense-in-depth protections against clickjacking, MIME-type sniffing, cross-domain policy abuse, and XSS attacks.
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= 5.1.2= 5.5.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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Couchbase Server versionQuery the Couchbase Server admin API (port 8091) or check the product version through the Couchbase Web Console under Settings > About, or run: cb_version_info or check installed package versionAffected if Installed version is exactly 5.1.2 or exactly 5.5.0 (other versions may also be affected but only these are confirmed in the advisory)
-
Confirm Views REST API is accessibleVerify that the Views REST API endpoint is reachable on port 8092. This is typically used for querying views/design documents at paths like /_design/<design>/_view/<view>Affected if Port 8092 is open and the Views REST API responds to HTTP requests
-
Capture HTTP response headers from Views APISend an HTTP GET request to a Views REST API endpoint (for example: http://localhost:8092/<bucket>/_design/<doc>/_view/<view>) and capture the response headers. Use curl -I or a similar tool to inspect headersAffected if The Views REST API returns an HTTP 200 or other response with headers present
-
Inspect for missing security headersExamine the response headers for the presence of all four security headers: X-Frame-Options, X-Content-Type-Options, X-Permitted-Cross-Domain-Policies, and X-XSS-ProtectionAffected if Any or all of these four headers are absent from the Views API response
If Couchbase Server version is 5.1.2 or 5.5.0 AND the Views REST API on port 8092 responds without one or more of the four security headers (X-Frame-Options, X-Content-Type-Options, X-Permitted-Cross-Domain-Policies, X-XSS-Protection), then the environment is affected by this CVE.
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.
From vendor dataUpgrade to Couchbase Server 6.0.2 or later where headers are included; alternatively, add these headers at the reverse proxy or load balancer level.
- 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-2019-11464 — 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-2019-11464 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