CVE-2024-56351
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 2024.12 access tokens were not revoked after removing user roles
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 confidenceIn JetBrains TeamCity versions prior to 2024.12, when administrators removed user roles from accounts, the associated access tokens were not automatically revoked. This means users whose roles were removed could continue using existing tokens to authenticate and access TeamCity resources they should no longer have permission to use.
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< 2024.12CVSS 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
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Check TeamCity versionNavigate to Administration > Global Settings or access the TeamCity welcome page > About. Alternatively, check the version file in the TeamCity data directory under config/internal.properties.Affected if The installed version is earlier than 2024.12 (for example, 2024.11, 2024.10, etc.)
-
Identify users with access tokensGo to Administration > User Management > Users. For each user, check the Authentication Tokens tab to see if any access tokens are currently issued and active.Affected if There are active access tokens in the system for any user account.
-
Review role assignment historyExamine the audit log at Administration > Audit Log. Look for events where user roles were removed. Cross-reference these users against those who still have active authentication tokens.Affected if Any user appears in the audit log as having had roles removed while still possessing valid active tokens.
-
Check recent authentication activityReview TeamCity authentication logs (typically in <TeamCity data directory>/logs/teamcity-auth.log). Look for successful token-based authentications from users whose roles have been modified after the authentication event.Affected if A user with previously revoked roles successfully authenticated using a token after their role removal date.
If your TeamCity version is before 2024.12 and you have users who have had roles removed but still possess active access tokens, your environment is affected by this vulnerability.
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 · scoped2024.12
Upgrade to TeamCity 2024.12 or later, which contains the fix for this issue. Alternatively, manually review and revoke any outstanding access tokens for users whose roles have been modified.
TeamCity 2024.12
- Ensure you have a complete backup of your TeamCity data directory and database before upgrading
- Review the TeamCity upgrade documentation for your current version
- Download TeamCity 2024.12 or later from the official JetBrains website
- Stop the TeamCity server
- Execute the upgrade installer or deploy the new version
- Start the TeamCity server and verify all services are running
- Test that user role changes now properly revoke associated access tokens
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-56351 — 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-56351 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