Credential disclosure via serializable settings object
Published Dec 4, 2023 · Updated May 7, 2026
Sensitive-information exposure in Google Cloud Firestore Node.js Client before 6.1.0 allows local users to read service-account keys from logs. The _settings property remained serializable, so JSON.stringify on Firestore objects copied its credentials, including private_key, into log output. Exposure requires an application to log a Firestore object and attackers to have log-read access; the published impact is credential disclosure without integrity or availability loss.
Summary
What happened
Sensitive-information exposure in Google Cloud Firestore Node.js Client before 6.1.0 allows local users to read service-account keys from logs. The _settings property remained serializable, so JSON.stringify on Firestore objects copied its credentials, including private_key, into log output. Exposure requires an application to log a Firestore object and attackers to have log-read access; the published impact is credential disclosure without integrity or availability loss.
The record
- CVE
- CVE-2023-6460
- Published
- Dec 4, 2023
- Updated
- May 7, 2026
- Vendor
- Product
- Cloud Firestore Node.js Client
- Classifications
- CWE-922, CWE-532, T1552.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Dec 4, 2023CVE publishedPublication date reported by the CVE source.
- May 7, 2026Record 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=0 <6.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