CVE-2024-32474: Sentry's superuser cleartext password leaked in logs
Impact When authenticating as a superuser to a self-hosted Sentry instance with a username and password, the password is leaked as cleartext in logs under the event: auth-index.validatesuperuser. An attacker with access to the log data could use these leaked credentials to login to the Sentry system as superuser.
Patches - Self-hosted users on affected versions should upgrade to 24.4.1 or later. - Sentry SaaS users do not need to take any action. This vulnerability is not applicable to SaaS.
Workarounds Users can configure the logging level to exclude logs of the INFO level and only generate logs for levels at WARNING or higher. For details on configuring self-hosted Sentry's logging level see our documentation at: https://develop.sentry.dev/config/#logging
References - Bug introduced in https://github.com/getsentry/sentry/pull/66393 - Security fix in https://github.com/getsentry/sentry/pull/69148
Other sources
Sentry is an error tracking and performance monitoring platform. Prior to 24.4.1, when authenticating as a superuser to Sentry with a username and password, the password is leaked as cleartext in logs under the event: auth-index.validatesuperuser. An attacker with access to the log data could use these leaked credentials to login to the Sentry system as superuser. Self-hosted users on affected versions should upgrade to 24.4.1 or later. Users can configure the logging level to exclude logs of the INFO level and only generate logs for levels at WARNING or more.
— MITRE
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-32474?
CVE-2024-32474 is a high severity vulnerability that exposes superuser passwords in cleartext in logs.
How do I fix CVE-2024-32474?
To fix CVE-2024-32474, upgrade your Sentry instance to version 24.4.1 or later.
What does CVE-2024-32474 affect?
CVE-2024-32474 affects Sentry versions between 24.3.0 and 24.4.1.
What are the consequences of CVE-2024-32474?
The consequences of CVE-2024-32474 include the potential unauthorized access to a Sentry instance through leaked superuser credentials.
How can I mitigate CVE-2024-32474 if I cannot upgrade?
If you cannot upgrade due to dependencies, restrict access to log files and monitor for unauthorized access.