CVE-2024-41656: Sentry vulnerable to stored Cross-Site Scripting (XSS)
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 CSPREPORTONLY = False (enforcing mode). This will mitigate the risk of XSS.
References Sentry Docs: Integration platform / Create an External Issue Sentry Docs: Self-hosted CSP The fix: https://github.com/getsentry/sentry/pull/74648 PortSwigger: Stored XSS
Other sources
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 CSPREPORTONLY = False (enforcing mode). This will mitigate the risk of cross-site scripting.
— MITRE
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2024-41656?
CVE-2024-41656 has been classified as a medium severity vulnerability due to its potential for exploitation via Stored Cross-Site Scripting (XSS).
How do I fix CVE-2024-41656?
To fix CVE-2024-41656, upgrade to Sentry version 24.7.1 or later to mitigate the XSS vulnerability.
What type of attack does CVE-2024-41656 allow?
CVE-2024-41656 allows for Stored Cross-Site Scripting (XSS) attacks through unsanitized HTML payloads.
Which versions of Sentry are affected by CVE-2024-41656?
CVE-2024-41656 affects Sentry versions from 10.0.0 up to, but not including, 24.7.1.
Where can I find more information about CVE-2024-41656?
More information about CVE-2024-41656 can be found in the Sentry security advisories and relevant GitHub discussions.