Account impersonation via GitLab authentication
Published Feb 25, 2022 · Updated Aug 3, 2024
Authentication impersonation in JetBrains TeamCity before 2021.1.4 allows remote attackers to assume a user's identity through GitLab login. JetBrains has not published the authentication-handler flaw or the exact validation error that permits one GitLab identity to be accepted as another. Reachability requires TeamCity's GitLab authentication integration, and a successful login grants the impersonated account's TeamCity access.
Summary
What happened
Authentication impersonation in JetBrains TeamCity before 2021.1.4 allows remote attackers to assume a user's identity through GitLab login. JetBrains has not published the authentication-handler flaw or the exact validation error that permits one GitLab identity to be accepted as another. Reachability requires TeamCity's GitLab authentication integration, and a successful login grants the impersonated account's TeamCity access.
The record
- CVE
- CVE-2022-24331
- Published
- Feb 25, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 25, 2022CVE 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