En bref
- CVE-2024-41656 est une vulnérabilité MOYENNE (CVSS 5.4) touchant sentry, sentry (sentry).
- Probabilité d'exploitation dans les 30 prochains jours (EPSS) : 0.47%, plus élevée que 40.5% des vulnérabilités.
- Correctif : mettre à jour vers 24.7.1 ou plus récent.
| Package | Affected versions | Patched versions |
|---|
| sentry PyPI | ≥ 10.0.0, < 24.7.1
| 24.7.1
|
| sentry | ≥ 10.0.0, < 24.7.1
| 24.7.1
|
Description
Impact
An unsanitized payload sent by an Integration platform integration allows the storage of arbitrary HTML tags on the Sentry side. This payload could subsequently be rendered on the Issues page, creating a Stored Cross-Site Scripting (XSS) vulnerability. This vulnerability might lead to the execution of arbitrary scripts in the context of a user’s browser.
Self-hosted Sentry users may be impacted if untrustworthy Integration platform integrations send external issues to their Sentry instance.
Patches
The patch has been released in Sentry 24.7.1
Workarounds
For Sentry SaaS customers, no action is needed. This has been patched on July 22, and even prior to the fix, the exploitation was not possible due to the strict Content Security Policy deployed on sentry.io site.
For self-hosted users, we strongly recommend upgrading Sentry to the latest version. If it is not possible, you could enable CSP on your self-hosted installation with CSP_REPORT_ONLY = False (enforcing mode). This will mitigate the risk of XSS.
References
NVD description
Sentry is an error tracking and performance monitoring platform. Starting in version 10.0.0 and prior to version 24.7.1, an unsanitized payload sent by an Integration platform integration allows storing arbitrary HTML tags on the Sentry side with the subsequent rendering them on the Issues page. Self-hosted Sentry users may be impacted in case of untrustworthy Integration platform integrations sending external issues from their side to Sentry. A patch has been released in Sentry 24.7.1. For Sentry SaaS customers, no action is needed. This has been patched on July 23, and even prior to the fix, the exploitation was not possible due to the strict Content Security Policy deployed on sentry.io site. For self-hosted users, the maintainers of Sentry strongly recommend upgrading Sentry to the latest version. If it is not possible, one could enable CSP on one's self-hosted installation with `CSP_REPORT_ONLY = False` (enforcing mode). This will mitigate the risk of cross-site scripting.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free