CVE-2024-45391: Tina search token leak via lock file in TinaCMS
Impact Tina search token leaked via lock file (tina-lock.json) in TinaCMS. Sites building with @tinacms/cli < 1.6.2 that use a search token are impacted.
If your Tina-enabled website has search setup, you should rotate that key immediately.
Patches This issue has been patched in @tinacms/cli@1.6.2
Workarounds Upgrading, and rotating search token is required for the proper fix.
References https://github.com/tinacms/tinacms/pull/4758
Other sources
Tina is an open-source content management system (CMS). Sites building with Tina CMS's command line interface (CLI) prior to version 1.6.2 that use a search token may be vulnerable to the search token being leaked via lock file (tina-lock.json). Administrators of Tina-enabled websites with search setup should rotate their key immediately. This issue has been patched in @tinacms/cli version 1.6.2. Upgrading and rotating the search token is required for the proper fix.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-45391?
CVE-2024-45391 has been classified as a significant vulnerability due to the potential leakage of search tokens.
How do I fix CVE-2024-45391?
To fix CVE-2024-45391, upgrade @tinacms/cli to version 1.6.2 or higher immediately.
What impact does CVE-2024-45391 have on my website?
CVE-2024-45391 can lead to exposure of sensitive search tokens, compromising the security of your TinaCMS-enabled site.
Which versions of software are affected by CVE-2024-45391?
CVE-2024-45391 affects all versions of @tinacms/cli prior to 1.6.2.
What should I do if I have been impacted by CVE-2024-45391?
If impacted by CVE-2024-45391, it is essential to rotate the leaked search token as soon as possible.