Loading vulnerability…
A vulnerability in JetBrains TeamCity prior to version 2021.2.1 allowed attackers to perform URL injection, which could be leveraged to conduct Cross-Site Request Forgery (CSRF) attacks. The flaw existed due to insufficient validation of user-supplied input in URLs, enabling attackers to craft malicious links that, when visited by authenticated users, could trigger unintended actions within TeamCity.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept exploit for CVE-2022-24342, a vulnerability in JetBrains TeamCity (versions prior to 2021.2.1) that allows account takeover via a CSRF attack in the GitHub OAuth2 authentication flow. The repository contains three files: a README.md with detailed instructions and background, a Python exploit script (exploit.py), and a requirements.txt listing dependencies (requests, fastapi, uvicorn). The exploit works by running a FastAPI web server that acts as a malicious OAuth2 application. The attacker sends a crafted link to the victim, which, when visited, manipulates the OAuth2 flow to link the victim's TeamCity account to the attacker's GitHub account. The exploit leverages network-based attack vectors and requires the attacker to set up a public-facing server (e.g., via ngrok). The main endpoints involved are the /exploit and /callback routes on the attacker's server, and the OAuth2 endpoints on the target TeamCity instance and GitHub. The exploit is a functional proof-of-concept and demonstrates the vulnerability's impact but does not include weaponized or automated post-exploitation features.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.