Approved changes feed: RSS · Atom
cpe:2.3:a:getsentry:sentry:-:*:*:*:*:*:*:*
part: a version: - update: *
| Vendor | Getsentry (15a72c39-e970-572b-a1f7-7c54bad269e6) |
|---|---|
| Product | Sentry (ba6cc7d1-37ed-557b-ac3e-4d690c809a8f) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-32474 |
vulnerable | 2026-06-08 06:35:33.181770 |
Sentry's superuser cleartext password leaked in logs
HIGH (7.3)
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.validate_superuser`. 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.
Published: 2024-04-18T19:50:44.541Z
Updated: 2024-08-02T02:13:39.118Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.