Skip to content

Sentry's improper authentication on SAML SSO process allows user impersonation

Critical severity GitHub Reviewed Published Jan 15, 2025 in getsentry/sentry • Updated Jan 15, 2025

Package

pip sentry (pip)

Affected versions

>= 21.12.0, < 25.1.0

Patched versions

25.1.0

Description

Impact

A critical vulnerability was discovered in the SAML SSO implementation of Sentry. It was reported to us via our private bug bounty program.

The vulnerability allows an attacker to take over any user account by using a malicious SAML Identity Provider and another organization on the same Sentry instance. The victim email address must be known in order to exploit this vulnerability.

Patches

  • Sentry SaaS: The fix was deployed on Jan 14, 2025.
  • Self-Hosted Sentry: If only a single organization is allowed (SENTRY_SINGLE_ORGANIZATION = True), then no action is needed. Otherwise, users should upgrade to version 25.1.0 or higher.

Workarounds

No known workarounds.

References

References

@oioki oioki published to getsentry/sentry Jan 15, 2025
Published by the National Vulnerability Database Jan 15, 2025
Published to the GitHub Advisory Database Jan 15, 2025
Reviewed Jan 15, 2025
Last updated Jan 15, 2025

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Weaknesses

CVE ID

CVE-2025-22146

GHSA ID

GHSA-7pq6-v88g-wf3w

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.