dbcve.org
TeamcityApplication · Jetbrains

CVE-2024-35301

MEDIUM · 5.5 CVSS v3.1 Published 2024-05-16
Fix available
A fix is available. Upgrade to 2024.03.1 or later.
See remediation →
61/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 2024.03.1 commit status publisher didn't check project scope of the GitHub App token

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 confidence

In JetBrains TeamCity versions prior to 2024.03.1, the commit status publisher feature failed to properly validate the project scope of GitHub App tokens. This authorization bypass could allow a GitHub App token with restricted project permissions to be used to post commit statuses to repositories outside its intended scope.

MitigationUpgrade to TeamCity 2024.03.1 or later which implements proper GitHub App token scope validation in the commit status publisher.

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.1

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
High
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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

  1. Check TeamCity version
    Access the TeamCity administration dashboard and navigate to 'Administration > Server Administration' or check the login page footer for the version number
    Affected if The installed version is any release prior to 2024.03.1
  2. Identify commit status publisher configurations
    Navigate to 'Administration > Integrations > Commit Status Publisher' in the TeamCity web interface to list all configured commit status publisher instances
    Affected if Any commit status publisher instance is configured with a GitHub App authentication type
  3. Review GitHub App token configurations
    Examine each commit status publisher configuration using GitHub App authentication - check the associated GitHub App settings and its granted repository permissions
    Affected if A GitHub App is configured with restricted project/repository scope permissions and is used in the commit status publisher for repositories outside that scope
  4. Verify repository scope mappings
    Compare the list of repositories configured in each commit status publisher against the repositories the associated GitHub App has been granted access to in GitHub
    Affected if A commit status publisher targets repositories that are not included in the GitHub App's authorized repository list
  5. Audit commit status push activity
    Review TeamCity build logs and audit trails for commit status publisher events - look for status updates pushed to repositories outside the expected scope
    Affected if Commit status entries appear in GitHub repositories that the GitHub App should not have access to based on its configured permissions

A user is affected if running TeamCity version prior to 2024.03.1 AND the commit status publisher feature is configured with a GitHub App that has limited repository permissions but is posting statuses to repositories outside its authorized scope.

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.1 or later
Fixed in 2024.03.1
Interim mitigation

Upgrade to TeamCity 2024.03.1 or later which implements proper GitHub App token scope validation in the commit status publisher.

Recommended fix High confidence

2024.03.1

  1. 1. Back up your current TeamCity installation, including the <TeamCity home>/data directory and configuration files.
  2. 2. Review the TeamCity 2024.03.1 release notes for any specific upgrade requirements or known issues.
  3. 3. Download TeamCity 2024.03.1 from the official JetBrains website (www.jetbrains.com).
  4. 4. Stop the TeamCity server service.
  5. 5. Install TeamCity 2024.03.1 following the standard upgrade procedure, preserving your existing data directory.
  6. 6. Start the TeamCity server and verify the upgrade was successful.
  7. 7. Verify that the GitHub App token project scope checking is now functioning correctly in the commit status publisher settings.
Caveat Standard TeamCity upgrade precautions apply; test in non-production environment first

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
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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