Security readout for executives and security teams
Plain-English summary
CVE-2023-6460 is a medium-severity information leak in Google’s nodejs-firestore library. If developers logged certain internal settings objects, a Firestore key could be written into logs. The business risk is unauthorized disclosure to anyone who can read those logs, not direct remote system takeover.
Executive priority
Prioritize for teams using nodejs-firestore in production, especially where logs are broadly accessible or retained long-term. Treat as a confidentiality issue requiring dependency upgrade and log review, not an emergency remote-code-execution event.
Technical view
The issue is CWE-922: sensitive information stored in logs. Logging objects through this._settings could include the Firestore key. The CVSS 3.1 score is 4.0 with local access, high privileges, high complexity, and user interaction reflected in the vector. Google recommends upgrading to nodejs-firestore 6.1.0.
Likely exposure
Exposure is most likely in applications using nodejs-firestore where developers logged this._settings or related objects, and where application, platform, or centralized logs are accessible to staff or systems beyond intended administrators.
Exploitation context
No active exploitation is indicated in the provided sources, and the CVE is not listed as KEV. Exploitation depends on the key actually being logged and an actor having read access to those logs.
Researcher notes
Public details are limited. The source bundle names nodejs-firestore and recommends version 6.1.0, but does not provide a clear affected version range beyond the CVE metadata. Validate against the GitHub pull request and Google bug report before making broad exposure claims.
Mitigation direction
- Upgrade nodejs-firestore to version 6.1.0 or later per Google’s recommendation.
- Remove logging of this._settings or sensitive configuration objects.
- Restrict access to application and centralized logs.
- Review historical logs for exposed Firestore keys.
- Rotate affected keys if exposure is confirmed.
Validation and detection
- Inventory applications using nodejs-firestore.
- Confirm deployed versions include the 6.1.0 fix.
- Review code for logging of this._settings or settings objects.
- Check log stores for Firestore key material.
- Verify log access is limited to authorized personnel.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-922: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-6460 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:N/A:N0.33.6GoogleVulnerability scoring details
Base CVSS 3.1 score
4MediumVector: CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/googleapis/nodejs-firestore/pull/1742CVE reference, Google
- https://bughunters.google.com/reports/vrp/KNvgo1WijCVE reference, Google
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insecure Storage of Sensitive Information
Insecure Storage of Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.