CVE-2022-32559
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 before 7.0.4. Random HTTP requests lead to leaked metrics.
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 confidenceCouchbase Server before version 7.0.4 contains an information disclosure vulnerability where arbitrary or random HTTP requests can cause the server to leak internal metrics. This metrics leakage could expose sensitive system information to unauthenticated remote attackers.
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.0.0, < 7.0.4CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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.
-
Determine installed Couchbase Server versionRun the command to retrieve the Couchbase Server version (typically via command line tool or check server diagnostics)Affected if The installed version is 4.0.0 or higher but lower than 7.0.4
-
Verify HTTP service exposureCheck network configuration to determine if Couchbase HTTP ports (default 8091, 18091) are accessible from untrusted network segments or the public internetAffected if HTTP management ports are exposed to unauthenticated or untrusted remote attackers
-
Review metrics access patternsExamine server access logs and audit logs for unusual or unexpected metrics endpoint requests from external IP addressesAffected if Logs show metrics endpoints being accessed by unknown or unauthorized remote clients
A user is affected if Couchbase Server version is between 4.0.0 and 7.0.4 (exclusive) AND the HTTP management interface is reachable by unauthenticated remote attackers who could request metrics endpoints.
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.0.4
Upgrade Couchbase Server to version 7.0.4 or later to remediate this vulnerability. If immediate upgrade is not feasible, restrict HTTP access to the server and monitor for unusual metrics access patterns.
7.0.4 or later
- Review the official Couchbase Server upgrade documentation at docs.couchbase.com for your current version
- Perform a full backup of all Couchbase buckets and cluster configuration
- Ensure your environment meets the prerequisites for version 7.0.4
- Plan for adequate maintenance window as upgrade may require cluster rebalancing
- Execute the upgrade following Couchbase's recommended rolling upgrade procedure if possible
- After upgrade, verify that all buckets, views, and queries are functioning correctly
- Confirm the vulnerability is resolved by ensuring metrics are no longer leaked on random HTTP requests
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-32559 — 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-2022-32559 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