dbcve.org
Sensitive Information in LogsWeakness · CWE-532

CVE-2025-8864

MEDIUM · 6.8 CVSS v4.0 Published 2025-08-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Zero-click

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 · unedited
Shared Access Signature token is not masked in the backup configuration response and is also exposed in the yb_backup 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 confidence

A Shared Access Signature (SAS) token exposure vulnerability exists in YugaByte DB's backup configuration. The sensitive SAS tokens are returned in plaintext within backup configuration API responses and are also written in plaintext to the yb_backup logs, allowing unauthorized access to these credentials.

MitigationImplement token masking in backup configuration response serialization to replace the full SAS token with a redacted placeholder (e.g., '***'). Additionally, configure log sanitization to detect and redact SAS tokens before写入日志.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Adjacent
Complexity
High
Privileges
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:H/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify YugaByte DB version
    Run 'yb_admin --version' or check the installed yugabytedb package version using your package manager
    Affected if Running any YugaByte DB version that supports backup configuration with SAS token-based storage authentication
  2. Review backup configuration for SAS token credentials
    Examine backup configuration settings (via CLI or API) for storage backends (particularly Azure Blob or other SAS-authenticated storage) and identify if SAS tokens are configured as credentials
    Affected if Backup configuration uses SAS tokens for authentication to storage
  3. Inspect backup configuration API responses
    Query the backup configuration API endpoint and examine the returned JSON/response body for any field containing the full SAS token value in plaintext
    Affected if API response returns unmasked SAS token values in credential fields
  4. Search yb_backup logs for plaintext tokens
    Search yb_backup log files (typically under /var/log/yugabyte or the configured log directory) for the presence of SAS token strings or patterns that resemble full token values
    Affected if Log files contain plaintext SAS tokens rather than redacted or masked placeholder values

If backup configurations use SAS tokens and either the backup configuration API responses or yb_backup logs expose these tokens in plaintext, the environment is affected by this vulnerability

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement token masking in backup configuration response serialization to replace the full SAS token with a redacted placeholder (e.g., '***'). Additionally, configure log sanitization to detect and redact SAS tokens before写入日志.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-8864 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-8864 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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