Sentry vulnerable to leaking superuser cleartext password in logs

CVE-2024-32474 → View on GitHub ↗ View on CVE.org ↗ View on NVD ↗

Description

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.validate_superuser. 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

Basic information

Type
reviewed
Severity
high
Advisory on GitHub
Open advisory ↗
Repository advisory
Open repository advisory ↗
Source code
Browse source ↗
Published (advisory)
2024-04-18 18:22:42 UTC
Updated
2024-04-19 21:43:14 UTC
GitHub reviewed
2024-04-18 18:22:42 UTC
NVD published
2024-04-18

EPSS Score

Score Percentile
0.73% 72.51%

CVSS Scores

Base score Version Severity Vector
7.3 3.1 —
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.

Identifiers

Type Value
GHSA GHSA-6cjm-4pxw-7xp9 ↗
CVE CVE-2024-32474 ↗

CWEs

CWE id Name
CWE-117 Improper Output Neutralization for Logs
CWE-312 Cleartext Storage of Sensitive Information

Credits

  • lluuaapp (finder)

Affected packages (1)

Vulnerable version ranges and first patched releases as published by GitHub.

Ecosystem Package Vulnerable range First patched Vulnerable functions
pip sentry >= 24.3.0, < 24.4.1 24.4.1 —

References

cvelogic Threat Intelligence