CVE-2023-6002
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 · uneditedYugabyteDB is vulnerable to cross site scripting (XSS) via log injection. Writing invalidated user input to log files can allow an unprivileged attacker to forge log entries or inject malicious content into the logs.
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 confidenceYugabyteDB is vulnerable to cross-site scripting (XSS) via log injection. An unprivileged attacker can supply malicious user input that gets written to log files without proper sanitization, allowing forged log entries or injection of malicious content that could execute when logs are viewed in a web interface.
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.14.0.0, < 2.14.14.0>= 2.16.0.0, < 2.16.8.0>= 2.18.0.0, < 2.18.4.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.
-
Check installed YugabyteDB versionRun 'ysqlsh --version' or 'yb-admin --version' from the command line, or query the system using 'SELECT * FROM system.local' to retrieve the version stringAffected if The version falls within these ranges: 2.14.0.0 to 2.14.13.x, 2.16.0.0 to 2.16.7.x, or 2.18.0.0 to 2.18.3.x
-
Verify web-based log viewing is accessibleCheck if the YugabyteDB web console or any HTTP-based log viewer is enabled and reachable (typically on port 7000 or 15433 for the master or tserver UI)Affected if Logs can be viewed through a web browser interface without additional authentication or with weak authentication
-
Confirm user input reaches logsReview application logs or audit configurations to determine if untrusted user input (such as query parameters, usernames, or session data) gets written to YugabyteDB log filesAffected if User-supplied data is directly written to logs without sanitization
You are affected if you run an affected YugabyteDB version (2.14.x before 2.14.14.0, 2.16.x before 2.16.8.0, or 2.18.x before 2.18.4.0) AND your logs are viewable through a web interface where crafted input could execute as JavaScript.
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 · scoped2.14.14.02.16.8.02.18.4.0
Implement input validation and output encoding/sanitization for all user-supplied data before logging. Ensure log viewing interfaces properly escape log content to prevent XSS execution.
2.14.14.0 (for 2.14.x) | 2.16.8.0 (for 2.16.x) | 2.18.4.0 (for 2.18.x)
- 1. Identify the current YugabyteDB version using 'yb-admin --version' or checking the cluster metrics
- 2. Based on your current major version, plan the upgrade path: If running 2.14.x upgrade to 2.14.14.0; If running 2.16.x upgrade to 2.16.8.0; If running 2.18.x upgrade to 2.18.4.0
- 3. Review YugabyteDB upgrade documentation at docs.yugabyte.com for your deployment type (kubernetes, on-premises, or cloud)
- 4. Create a backup of the cluster before upgrading
- 5. Perform the upgrade following the rolling upgrade procedure to maintain availability
- 6. Verify the upgrade completed successfully by checking cluster health and the new version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-6002 — 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-2023-6002 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