CVE-2024-23302
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 before 7.2.4 has a private key leak in goxdcr.log.
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 before 7.2.4 inadvertently write private cryptographic keys to the goxdcr.log file. This log file may be accessible to unauthorized users or systems, potentially exposing the private key and enabling decryption of communications or service impersonation.
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< 7.2.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
- 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.
-
Identify installed Couchbase Server versionRun 'couchbase-cli server-info' or check the Couchbase Web UI under 'Server Nodes' to view the installed version numberAffected if The version is lower than 7.2.4 (e.g., 7.2.3, 7.2.2, 7.1.x, etc.)
-
Locate the goxdcr.log fileSearch for 'goxdcr.log' in the Couchbase Server logs directory, typically found under the installation path or /opt/couchbase/var/lib/couchbase/logs/Affected if The log file exists and was created or modified before upgrading to 7.2.4 or later
-
Inspect goxdcr.log for private key patternsOpen the goxdcr.log file and search for strings containing '-----BEGIN PRIVATE KEY-----', 'BEGIN RSA PRIVATE KEY', 'BEGIN EC PRIVATE KEY', or other PEM-encoded private key headersAffected if The log file contains any PEM-formatted private key blocks or base64-encoded key material
-
Verify log file access permissionsCheck file permissions on goxdcr.log using 'ls -la' to determine if unauthorized users or groups have read accessAffected if The log file has world-readable permissions or permissions allowing access to non-privileged users
You are affected if your Couchbase Server version is below 7.2.4 and the goxdcr.log file contains PEM-encoded private key material or displays world-readable permissions.
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.4
Upgrade Couchbase Server to version 7.2.4 or later to remediate the private key leak. Additionally, audit and securely dispose of any potentially compromised log files containing the exposed private key.
7.2.4 or later
- Upgrade Couchbase Server to version 7.2.4 or later to resolve the private key leak in goxdcr.log
- After upgrade, verify that goxdcr.log no longer contains any private key information
- Ensure log rotation policies are in place to properly manage log files containing sensitive information
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-2024-23302 — 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-23302 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