SAS token disclosure via unmasked backup output
Published Aug 11, 2025 · Updated Aug 11, 2025
Token exposure in YugabyteDB Anywhere 2.23.0.0 and 2024.1.0.0 through 2024.1.2.0 reveals Azure SAS tokens to remote authenticated users. The backup configuration response returns the Shared Access Signature without masking, and yb_backup writes the same secret into log entries. Access requires a highly privileged account on an adjacent network, and a disclosed token grants the storage permissions encoded in that token.
Summary
What happened
Token exposure in YugabyteDB Anywhere 2.23.0.0 and 2024.1.0.0 through 2024.1.2.0 reveals Azure SAS tokens to remote authenticated users. The backup configuration response returns the Shared Access Signature without masking, and yb_backup writes the same secret into log entries. Access requires a highly privileged account on an adjacent network, and a disclosed token grants the storage permissions encoded in that token.
The record
- CVE
- CVE-2025-8864
- Published
- Aug 11, 2025
- Updated
- Aug 11, 2025
- Vendor
- YugabyteDB, Inc.
- Product
- YugabyteDB Anywhere
- Classifications
- CWE-532, CAPEC-215, T1552.001
- Attack vector
- adjacent
- Privileges
- admin
Timeline
How it unfolded
- Aug 11, 2025CVE publishedPublication date reported by the CVE source.
- Aug 11, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2024.1.0.0 <2024.1.3.0
- Affected versionversion=2.23.0.0 <2.23.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo