Confidentiality loss via unchecked SSO redirect
Published May 11, 2021 · Updated Aug 3, 2024
Open redirect in JetBrains TeamCity before 2020.2.3 allows remote attackers to redirect GitHub SSO token exchanges to untrusted URIs. GitHub SSO redirect_uri validation accepts an attacker-controlled callback destination without confirming that it is an approved URI. Exploitation requires the GitHub SSO flow, and the published record establishes confidentiality loss but does not disclose the exact data exposed.
Summary
What happened
Open redirect in JetBrains TeamCity before 2020.2.3 allows remote attackers to redirect GitHub SSO token exchanges to untrusted URIs. GitHub SSO redirect_uri validation accepts an attacker-controlled callback destination without confirming that it is an approved URI. Exploitation requires the GitHub SSO flow, and the published record establishes confidentiality loss but does not disclose the exact data exposed.
The record
- CVE
- CVE-2021-31913
- Published
- May 11, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-601, CWE-354, T1528
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 11, 2021CVE publishedPublication date reported by the CVE source.
- Aug 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Weakness, pattern, technique
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