Search token disclosure via serialized search configuration
Published Sep 3, 2024 · Updated Sep 3, 2024
Sensitive information exposure in TinaCMS before 1.6.2 allows remote attackers to read a search token from tina-lock.json. The CLI Codegen path retained the search object in schema configuration when serializing generated data, causing the search indexer token to enter the lock file. Exposure requires a site built with the CLI and configured for search; disclosure is limited to the stored search credential.
Summary
What happened
Sensitive information exposure in TinaCMS before 1.6.2 allows remote attackers to read a search token from tina-lock.json. The CLI Codegen path retained the search object in schema configuration when serializing generated data, causing the search indexer token to enter the lock file. Exposure requires a site built with the CLI and configured for search; disclosure is limited to the stored search credential.
The record
- CVE
- CVE-2024-45391
- Published
- Sep 3, 2024
- Updated
- Sep 3, 2024
- Vendor
- TinaCMS
- Product
- TinaCMS
- Classifications
- CWE-200
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 3, 2024CVE publishedPublication date reported by the CVE source.
- Sep 3, 2024Record 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=< 1.6.2
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