CVE-2024-25673
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.6.x before 7.6.2, 7.2.x before 7.2.6, and all earlier versions allows HTTP Host header injection.
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 versions before 7.6.2 and 7.2.6 are vulnerable to HTTP Host header injection. The application processes the Host header value in server-side operations without proper validation, allowing attackers to manipulate the header to conduct attacks such as cache poisoning, password reset poisoning, or potentially SSRF.
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.2.6>= 7.6.0, < 7.6.2CVSS 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 versionRun 'couchbase-cli server-info' or check the Couchbase Web Console login page footer, or inspect server logs for version stringsAffected if version cannot be determined or is below 7.2.6 or between 7.6.0 and 7.6.2
-
Compare version against affected rangesVerify the installed version falls outside the safe ranges: 7.2.6+ or 7.6.2+. Versions < 7.2.6 or >= 7.6.0 but < 7.6.2 are vulnerableAffected if installed version is < 7.2.6 or >= 7.6.0 but < 7.6.2
-
Confirm HTTP service exposureCheck if the Couchbase Server HTTP interface (ports 8091, 18091, or custom httpd ports) is accessible from network segments where untrusted users could send crafted requestsAffected if HTTP ports are exposed to untrusted sources and version is in vulnerable range
Environment is affected if Couchbase Server version is < 7.2.6 or >= 7.6.0 but < 7.6.2 AND the HTTP interface accepts requests with arbitrary Host headers.
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.2.67.6.2
Upgrade Couchbase Server to version 7.6.2+, 7.2.6+, or later. Alternatively, configure upstream web servers or load balancers to validate, normalize, or reject suspicious Host headers before they reach the application.
7.2.6 or 7.6.2 (preferred: 7.6.2)
- 1. Back up your Couchbase Server data and cluster configuration before upgrading.
- 2. Download Couchbase Server version 7.2.6 or 7.6.2 from the official Couchbase downloads page.
- 3. If running a cluster, follow Couchbase's rolling upgrade procedure to minimize downtime: for each node, stop the Couchbase service, upgrade the software, and rebalance the cluster.
- 4. After upgrading all nodes, verify the cluster is healthy using the Couchbase Admin Console or CLI.
- 5. Test application connectivity to ensure the HTTP Host header injection is no longer exploitable.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-25673 — 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-2024-25673 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