Headline
GHSA-6cjm-4pxw-7xp9: Sentry vulnerable to leaking superuser cleartext password in logs
Impact
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.validate_superuser
. An attacker with access to the log data could use these leaked credentials to login to the Sentry system as superuser.
Patches
- Sentry SaaS users do not need to take any action.
- Self-hosted users on affected versions should upgrade to 24.4.1 or later.
Workarounds
Users can configure the logging level to exclude logs of the INFO
level and only generate logs for levels at WARNING
or more. 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
Affected versions
>= 24.3.0, < 24.4.1
Description
Impact
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.validate_superuser. An attacker with access to the log data could use these leaked credentials to login to the Sentry system as superuser.
Patches
- Sentry SaaS users do not need to take any action.
- Self-hosted users on affected versions should upgrade to 24.4.1 or later.
Workarounds
Users can configure the logging level to exclude logs of the INFO level and only generate logs for levels at WARNING or more. For details on configuring self-hosted Sentry’s logging level see our documentation at: https://develop.sentry.dev/config/#logging
References
- Bug introduced in getsentry/sentry#66393
- Security fix in getsentry/sentry#69148
References
- GHSA-6cjm-4pxw-7xp9
- getsentry/sentry#66393
- getsentry/sentry#69148
- getsentry/sentry@d5b3456
Published to the GitHub Advisory Database
Apr 18, 2024