CVE-2022-24334
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn JetBrains TeamCity before 2021.2.1, the Agent Push feature allowed selection of any private key on the server.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn JetBrains TeamCity before version 2021.2.1, the Agent Push feature contained an improper access control vulnerability that allowed authenticated users to select any private key stored on the TeamCity server, rather than being restricted to keys legitimately required for agent deployment. This could enable privilege escalation or unauthorized access to connected build agents.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2021.2.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check TeamCity server versionNavigate to Administration > Server Administration > Overview or check the login page footer for the version number. Compare against 2021.2.1.Affected if Version is lower than 2021.2.1
-
Verify Agent Push plugin statusGo to Administration > Plugins > Built-in Plugins and confirm the 'Agent Push' plugin is installed and enabled.Affected if Agent Push plugin is present and enabled on any version below 2021.2.1
-
Inspect private key storage configurationNavigate to Administration > Server Administration > SSH Keys or Agent Push settings page and list all stored private keys accessible through the server.Affected if Any private keys are stored on the TeamCity server and Agent Push is accessible to non-admin users
-
Review Agent Push access control settingsCheck Administration > User Management > Roles and Permissions for which users or groups have permission to use the Agent Push feature.Affected if Users other than trusted administrators have Agent Push permissions
-
Audit Agent Push usage logsReview TeamCity audit logs under Administration > Server Administration > Audit Log for any Agent Push operations that accessed private keys outside expected agent deployment scopes.Affected if Agent Push was used to access private keys by users without legitimate need
A user is affected if running TeamCity version below 2021.2.1 with the Agent Push feature enabled and accessible to users beyond trusted administrators.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2021.2.1
Upgrade JetBrains TeamCity to version 2021.2.1 or later. If immediate upgrading is not possible, restrict access to the Agent Push functionality to only trusted administrators and audit existing private key usage.
2021.2.1 or later
- Back up the TeamCity server data, configuration, and database according to JetBrains backup documentation
- Stop the TeamCity server service
- Download TeamCity 2021.2.1 or a later stable version from the official JetBrains website (https://www.jetbrains.com/teamcity/download/)
- Review the official TeamCity upgrade guide for your deployment type (tar.gz or Windows installer)
- Run the upgrade installation following JetBrains upgrade instructions - for tar.gz extraction, extract to a new directory and copy the 'conf' and 'logs' directories from the old installation
- Start the TeamCity server
- Log in as an administrator and verify the Agent Push feature configuration
- Verify that the private key selection is now properly restricted to authorized keys only
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24334 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-24334 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data