CVE-2024-36365
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 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5, 2024.03.2 a third-party agent could impersonate a cloud agent
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 versions prior to 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5, and 2024.03.2, a third-party agent could impersonate a cloud agent by exploiting an authentication weakness in the agent registration mechanism, allowing an unauthorized actor to gain the privileges of a legitimate cloud agent in the build infrastructure.
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< 2022.04.7>= 2022.10, < 2022.10.6>= 2023.05, < 2023.05.6>= 2023.11, < 2023.11.5>= 2024.03, < 2024.03.2CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Determine TeamCity server versionLog into the TeamCity web interface as administrator, then navigate to Administration → Server Administration → About, or access the /about.html page. The version number is displayed on this page. Alternatively, check the buildServerLogs directory for startup logs that contain the version, or query the TeamCity REST API endpoint /app/rest/server/version.Affected if The installed version is less than 2022.04.7, or between 2022.10.0-2022.10.5, or between 2023.05.0-2023.05.5, or between 2023.11.0-2023.11.4, or between 2024.03.0-2024.03.1.
-
Identify if cloud agents are configuredNavigate to Administration → Cloud Profiles in the TeamCity web interface. Review whether any cloud profiles (AWS, Azure, Google Cloud, or other) are defined and enabled. Also check Administration → Agent Cloud Credentials for any configured cloud credentials.Affected if Cloud agent profiles or cloud credentials are present and the server version falls within the affected ranges listed above.
-
Review registered agents for unauthorized entriesNavigate to Administration → Agents → Agent Management. Examine the list of registered agents, paying particular attention to agents marked as cloud agents. Check the Agent Details for the registration date, IP address, and other metadata to identify any suspicious or unexpected cloud agent registrations.Affected if Any cloud agent registration exists that was not initiated through the legitimate cloud profile workflow, especially if the agent claims elevated privileges or shows unusual metadata.
-
Check agent authorization settingsNavigate to Administration → Server Administration → Authentication Settings. Examine the authorization module configuration for agent registration. Look for settings related to 'authorized' vs 'unauthorized' agents and whether there are any exceptions or weak authentication methods enabled for agent connections.Affected if Agents are set to 'authorized' by default without proper verification, or unauthenticated agent registration is permitted.
A TeamCity installation is affected if it runs a version prior to the fixed releases AND has cloud agent profiles configured, allowing a third-party agent to potentially register as a cloud agent through the authentication weakness.
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 · scoped2022.04.72022.10.62023.05.6
Upgrade TeamCity server and agents to version 2022.04.7 or later for the 2022.04 line, 2022.10.6 or later for 2022.10, 2023.05.6 or later for 2023.05, 2023.11.5 or later for 2023.11, or 2024.03.2 or later for 2023.11+ lines; also audit existing agent registrations for unauthorized entries.
Upgrade to TeamCity 2024.03.2 (or the latest stable release) which contains the fix for all affected version ranges
- Identify the currently installed TeamCity version from the server administration interface
- Determine which version range your current installation falls into (< 2022.04.7, 2022.10.x, 2023.05.x, or 2023.11.x)
- Download the appropriate fixed version from www.jetbrains.com/teamcity/download: 2022.04.7 (if on < 2022.10), 2022.10.6 (if on 2022.10.x), 2023.05.6 (if on 2023.05.x), 2023.11.5 (if on 2023.11.x), or 2024.03.2 for the latest
- Review TeamCity upgrade documentation and perform a full backup of the TeamCity Data Directory and database
- Stop the TeamCity server and perform the upgrade installation
- Start the TeamCity server and verify all agents connect correctly
- Confirm the cloud agent impersonation vulnerability is resolved by validating agent authentication
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36365 — 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-2024-36365 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