dbcve.org
TeamcityApplication · Jetbrains

CVE-2024-36364

MEDIUM · 6.5 CVSS v3.1 Published 2024-05-29
Fix available
A fix is available. Upgrade to 2022.04.7 / 2022.10.6 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
In JetBrains TeamCity before 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 improper access control in Pull Requests and Commit status publisher build features was possible

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 · moderate confidence

Improper access control in TeamCity's Pull Requests and Commit status publisher build features allowed unauthorized manipulation of build status information. This could enable users to modify or spoof commit status checks and pull request feedback without proper authorization, potentially leading to bypass of CI/CD validation gates.

MitigationUpgrade TeamCity to version 2022.04.7, 2022.10.6, 2023.05.6, or 2023.11.5 or later. Review user permissions on build features and audit access logs for suspicious activity.

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
TeamcityApplication
Affected:< 2022.04.7>= 2022.10, < 2022.10.6>= 2023.05, < 2023.05.6>= 2023.11, < 2023.11.5

CVSS 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify TeamCity server version
    Log into TeamCity as administrator and navigate to Administration > About, or check the version displayed on the server login page
    Affected if The installed version is less than 2022.04.7, OR is 2022.10.x but less than 2022.10.6, OR is 2023.05.x but less than 2023.05.6, OR is 2023.11.x but less than 2023.11.5
  2. Locate Pull Requests build feature configurations
    Navigate to Administration > Build Features and review all build configurations for the 'Pull Requests' feature type, or inspect project build configuration XML files in the TeamCity data directory
    Affected if The Pull Requests build feature is enabled in any project or build configuration on a vulnerable TeamCity version
  3. Locate Commit Status Publisher build feature configurations
    Navigate to Administration > Build Features and review all build configurations for the 'Commit Status Publisher' feature type, or inspect project build configuration XML files in the TeamCity data directory
    Affected if The Commit Status Publisher build feature is enabled in any project or build configuration on a vulnerable TeamCity version
  4. Review user permissions on build features
    In TeamCity administration, go to Authentication > Roles or project-level user roles and verify which users or groups have permissions to modify or delete build features
    Affected if Users without administrative privileges have the ability to add, modify, or delete Pull Requests or Commit Status Publisher features, particularly in projects they do not own

You are affected if your TeamCity server version falls within any of the vulnerable ranges AND either the Pull Requests or Commit Status Publisher build features are enabled in your environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2022.04.7 / 2022.10.6 / 2023.05.6 or later
Fixed in 2022.04.72022.10.62023.05.6
Interim mitigation

Upgrade TeamCity to version 2022.04.7, 2022.10.6, 2023.05.6, or 2023.11.5 or later. Review user permissions on build features and audit access logs for suspicious activity.

Recommended fix High confidence

TeamCity 2023.11.5 or later stable release

  1. Review the TeamCity 2023.11.5 (or latest stable) release notes for any configuration or feature changes
  2. Create a complete backup of the TeamCity data directory (typically <TeamCity home>/data)
  3. Test the upgrade in a non-production environment to verify compatibility with your configurations and plugins
  4. Schedule a maintenance window for the upgrade
  5. Stop the TeamCity server service
  6. Install TeamCity 2023.11.5 or later (or apply the relevant patch for your version branch)
  7. Start the TeamCity server service
  8. Verify that the Pull Requests and Commit status publisher build features are functioning correctly post-upgrade
Caveat Review release notes for potential breaking changes between your current version and 2023.11.5; some plugins or configurations may require updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Teamcity Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36364 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-36364 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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