Cross-account OAuth token theft via credential misvalidation
Published Aug 9, 2023 · Updated Oct 3, 2024
Improper authentication in Sentry 10.0.0 through 23.7.1 allows remote authenticated users to obtain another user's OAuth access token. The OAuth token endpoint validates exchange credentials incorrectly and returns a valid token for a different user; Sentry has not disclosed the exact failed check. Exploitation requires a known client ID, prior authorization of the API application on the targeted account, a client-side exploit, and user interaction.
Summary
What happened
Improper authentication in Sentry 10.0.0 through 23.7.1 allows remote authenticated users to obtain another user's OAuth access token. The OAuth token endpoint validates exchange credentials incorrectly and returns a valid token for a different user; Sentry has not disclosed the exact failed check. Exploitation requires a known client ID, prior authorization of the API application on the targeted account, a client-side exploit, and user interaction.
The record
- CVE
- CVE-2023-39531
- Published
- Aug 9, 2023
- Updated
- Oct 3, 2024
- Vendor
- Sentry
- Product
- Sentry
- Classifications
- CWE-287, T1528
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 9, 2023CVE publishedPublication date reported by the CVE source.
- Oct 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 10.0.0, < 23.7.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo