GHSA-53vv-xm9f-mm82: Low severity npm/ghost vulnerability
Impact
Any staff-level user was able to determine the relative ordering of other staff users' hashed passwords. This does not directly disclose password hashes, and does not provide a practical path to recovering a password.
Vulnerable versions
This vulnerability is present in Ghost from v0.7.2 up to v6.64.0.
Patches
v6.64.0 contains a fix for this issue.
How to update
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.
References
Ghost thanks carfeii and Nhat Anh Vu for disclosing this vulnerability responsibly.
For more information
If you have any questions or comments about this advisory, email us at security@ghost.org.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/ghostto a version that resolves this vulnerability.Fixed in 6.64.0 - Upgrade
Upgrade
Ghostto a version that resolves this vulnerability.Fixed in 6.64.0
Event History
Frequently Asked Questions
What access would an attacker need to exploit this issue?
The attacker would need staff-level access to the Ghost instance. The advisory does not indicate that unauthenticated users can exploit it.
What information could be exposed?
A staff-level user could determine the relative ordering of other staff users' hashed passwords. The issue does not directly reveal password hashes and is not described as providing a practical way to recover passwords.
What should self-hosted deployments do?
Update Ghost to v6.64.0, which contains the fix. Docker-based deployments can update using the official Ghost Docker image, while Ghost-CLI installations should follow the documented Ghost update process.