dbcve.org
TeamcityApplication · Jetbrains

CVE-2024-36377

HIGH · 8.1 CVSS v3.1 Published 2024-05-29
Fix available
A fix is available. Upgrade to 2024.03.2 or later.
See remediation →
87/100
Remediation priority · High
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 2024.03.2 certain TeamCity API endpoints did not check user permissions

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

Certain TeamCity API endpoints before version 2024.03.2 lacked proper permission/authorization checks, allowing authenticated users to access functionality or data beyond their granted permissions through the API.

MitigationUpgrade TeamCity to version 2024.03.2 or later to obtain the patched version. Until then, restrict network access to API endpoints and monitor for unauthorized access patterns.

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:< 2024.03.2

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
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 checks

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

  1. Identify installed TeamCity version
    Access the TeamCity administration interface and navigate to the 'About' page, or check the buildServer.properties file for the version number
    Affected if The displayed version is less than 2024.03.2 (for example, 2024.03.1, 2023.x, or earlier)
  2. Confirm API endpoints are accessible
    Attempt to access a known TeamCity API endpoint such as /app/rest/server or /httpAuth/app/rest/users via HTTP request from an authenticated session
    Affected if API endpoints respond with data or error messages, indicating they are reachable and functional
  3. Verify authentication is enabled for API access
    Review the authentication configuration in TeamCity under 'Administration > Authentication' settings to confirm users can authenticate to the system
    Affected if User authentication is configured and functional, meaning authenticated users can make API requests
  4. Check for authorization configuration gaps
    Review user and group permissions in 'Administration > Users' and 'Administration > User Groups' to identify users with limited permissions who should not access certain data
    Affected if There exist users or groups whose permissions are intentionally restricted, and those restrictions are meant to prevent access to certain API resources

Your environment is affected if the installed TeamCity version is below 2024.03.2 and API endpoints are accessible to authenticated users with limited permissions.

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 2024.03.2 or later
Fixed in 2024.03.2
Interim mitigation

Upgrade TeamCity to version 2024.03.2 or later to obtain the patched version. Until then, restrict network access to API endpoints and monitor for unauthorized access patterns.

Recommended fix High confidence

TeamCity 2024.03.2 or later

  1. Backup your current TeamCity data and configuration files before starting the upgrade
  2. Download TeamCity 2024.03.2 or later from the official JetBrains website (www.jetbrains.com/teamcity/download)
  3. Stop the running TeamCity server
  4. Extract and install the new TeamCity 2024.03.2 version
  5. Start the TeamCity server and verify it runs without errors
  6. Log in to the TeamCity web interface and verify that the authorization fix is working by testing the previously vulnerable API endpoints with non-privileged users
  7. Review user permissions and roles to ensure proper access controls are in place
Caveat Standard TeamCity upgrade considerations apply - review JetBrains upgrade notes for your specific version path for any configuration or plugin compatibility issues

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36377 — 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-36377 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