CVE-2024-31134
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.03 authenticated users without administrative permissions could register other users when self-registration was disabled
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 confidenceIn JetBrains TeamCity before version 2024.03, an authorization flaw allowed any authenticated user (non-administrator) to register new user accounts even when self-registration was explicitly disabled. This bypasses the intended access control and could enable unauthorized user account creation.
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.03CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed TeamCity versionAccess the TeamCity web UI and check the version displayed at the bottom of any page, or query the /app/rest/server/version endpoint if you have API accessAffected if The installed version is any version prior to 2024.03 (e.g., 2023.11, 2023.05, etc.)
-
Confirm self-registration is disabledNavigate to Administration > Authentication > User Registration settings in the TeamCity web UI and verify that self-registration/registration for new users is turned offAffected if Self-registration is explicitly disabled in the configuration
-
Test non-admin user account creation capabilityLog in as a regular (non-administrator) authenticated user, then attempt to access the user registration/create new user functionality. Try navigating to the create new user page or using the REST API endpoint for user creation without admin privilegesAffected if A non-administrator authenticated user can successfully register/create new user accounts despite self-registration being disabled
-
Verify authorization settings for user managementReview the user roles and permissions in Administration > User Management to confirm that regular users should not have create user permissions, then attempt to create a user with such an account to confirm the bypassAffected if Non-admin users can create accounts when they should not have that permission based on their role configuration
You are affected if your TeamCity version is before 2024.03 AND self-registration is disabled AND any authenticated non-admin user can create new user accounts, bypassing the intended access control.
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.03
Upgrade TeamCity to version 2024.03 or later. After upgrading, verify that self-registration settings work correctly and that non-admin users cannot register other users.
TeamCity 2024.03
- 1. Back up your TeamCity database and configuration files according to the official backup documentation
- 2. Download TeamCity 2024.03 or later from the official JetBrains website (www.jetbrains.com/teamcity/download)
- 3. Stop the TeamCity server
- 4. Run the installer or extract the new version to replace the existing installation
- 5. Start the TeamCity server and verify the upgrade was successful
- 6. Verify that the vulnerability is fixed by attempting to confirm that non-admin users can no longer register other users when self-registration is disabled
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31134 — 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-31134 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