dbcve.org
TeamcityApplication · Jetbrains

CVE-2024-56349

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-20
Fix available
A fix is available. Upgrade to 2024.12 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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.12 improper access control allowed unauthorized users to modify build logs

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

JetBrains TeamCity before version 2024.12 contains an improper access control vulnerability that allows unauthorized users to modify build logs. This is an authorization bypass where the system fails to properly validate user permissions before allowing write access to build log entries.

MitigationUpgrade JetBrains TeamCity to version 2024.12 or later to remediate this vulnerability. Verify that build log modification is properly restricted to authorized users after the upgrade.

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

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

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

  1. Identify installed TeamCity version
    Navigate to Administration > Server Administration > Server Configuration, or check the login page footer which displays the version number. You can also query the REST API at /app/rest/server/version
    Affected if The installed version is any version prior to 2024.12 (e.g., 2024.11, 2024.10, earlier releases)
  2. Verify guest access configuration
    Go to Administration > Authentication > Guest User Settings, or check if guest login is enabled under Administration > Authentication > Users. Confirm whether guest or unauthenticated users have any access to the server
    Affected if Guest access is enabled and users can access the TeamCity web interface without authentication
  3. Check build configuration visibility settings
    Navigate to a project's Build Configuration settings > Permissions tab, or examine the 'Visible for' setting in each build configuration under Administration > Projects > [Project] > Build Configurations
    Affected if Build configurations are set to 'Visible for: All users' or 'Visible for: Guest users' allowing unauthorized access to build data
  4. Inspect build log access permissions
    Attempt to access a build's log via the web UI at /viewLog.html?buildId=X or via REST API at /app/rest/builds/id:X/log as an unauthenticated or low-privilege user. Check if write/modify operations on build logs are blocked
    Affected if Unauthenticated or unauthorized users can access and potentially modify build log entries without proper authorization checks

A user is affected if their TeamCity version is below 2024.12 AND the server allows any form of unauthenticated or unauthorized access that could permit modification of build log entries.

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.12 or later
Fixed in 2024.12
Interim mitigation

Upgrade JetBrains TeamCity to version 2024.12 or later to remediate this vulnerability. Verify that build log modification is properly restricted to authorized users after the upgrade.

Recommended fix High confidence

TeamCity 2024.12

  1. Back up your TeamCity data directory and database before upgrading
  2. Download TeamCity 2024.12 or later from the official JetBrains website
  3. Stop the TeamCity server
  4. Follow the official TeamCity upgrade instructions for your installation method
  5. Start the TeamCity server after upgrade completes
  6. Verify that build logs can only be modified by authorized users

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

Fix this in Teamcity Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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