CVE-2024-53253

Impact for SaaS Users

For Sentry SaaS users, we have confirmed that only a single application integration was impacted and the owner has rotated their Client Secret. We have also confirmed that no abuse of the leaked Client Secret has occurred.

Potential Impact for Self-Hosted Users

Sentry self-hosted does not ship with any application integrations. This could only impact self-hosted users that maintain their own integrations. In that case, search for a select-requester.invalid-response event. Please note that this error was also shared with another event unrelated to this advisory so you will also need to review the parameters logged for each named event. You may review select_requester.py for the instances where these errors can be generated. With the security fix this is no longer a shared event type.

References

• Bug introduced in https://github.com/getsentry/sentry/pull/79377
• Security fix in https://github.com/getsentry/sentry/pull/81038

During routine testing, we identified a scenario where a specific error message generated by our platform could include a plaintext Client ID and Client Secret for an application integration. The Client ID and Client Secret would not be displayed in the UI, but would be returned in the underlying HTTP response to the end user. This could occur under the following conditions:

• An app installation made use of a Search UI component with the async flag set to true (default: true),
• A user types types into the Search Component which creates a request to the third-party for search or query results, and
• That third-party response may then fail validation and Sentry would return the select-requester.invalid-response error code along with a serialized version of a Sentry application containing the integration Client Secret.

Should this error be found, it's reasonable to assume the potential exposure of an integration Client Secret. However, an ID and Secret pair alone does not provide direct access to any data. For that secret to be abused an attacker would also need to obtain a valid API token for a Sentry application.

CVE-2024-53253 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (24.11.1); upgrading removes the vulnerable code path.

Kodem intelligence

• Sentry SaaS users do not need to take any action.
• Sentry self-hosted users should upgrade to 24.11.1 or higher.

1. What is CVE-2024-53253? CVE-2024-53253 is a medium-severity security vulnerability in sentry (pip), affecting versions = 24.11.0. It is fixed in 24.11.1.
2. How severe is CVE-2024-53253? CVE-2024-53253 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of sentry are affected by CVE-2024-53253? sentry (pip) versions = 24.11.0 is affected.
4. Is there a fix for CVE-2024-53253? Yes. CVE-2024-53253 is fixed in 24.11.1. Upgrade to this version or later.
5. Is CVE-2024-53253 exploitable, and should I be worried? Whether CVE-2024-53253 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-53253 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-53253? Upgrade sentry to 24.11.1 or later.