npm · ghost
Ghost: Blind Password Hash Disclosure in Ghost Admin API
Any staff-level user was able to leak the hashed passwords of other staff users. An offline password-guessing attack against the hashes could lead to account takeover if successful, but Device Verification should have prevented an attacker from logging in with a recovered password. Depending on the database used, leaked hashes may not have had the correct casing for all characters, increasing the difficulty of a password-guessing attack.
This vulnerability is present in Ghost versions v6.54.0 and earlier.
v6.54.1 contains a fix for this issue.
For self-hosters using Docker, find Docker's official Ghost image here. Updating a Docker-based Ghost instance is documented here.
If your Ghost is a Ghost-CLI install see our documentation on updating it to the latest version here.
If upgrading immediately is not possible, ensure all staff users have Multi-factor Authentication (MFA) enabled. This will help prevent an attacker from logging in with any passwords that are successfully recovered from the leaked hashes.
Ghost thanks Chapman Schleiss for disclosing this vulnerability responsibly.
If you have any questions or comments about this advisory, email us at security@ghost.org.
Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.
Check my repoSources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.