CVE-2024-31136
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 2FA could be bypassed by providing a special URL parameter
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 confidenceJetBrains TeamCity versions before 2024.03 contain an authentication bypass vulnerability where two-factor authentication (2FA) can be circumvented by including a special URL parameter in requests. This allows attackers to potentially access accounts protected by 2FA without completing the second authentication factor.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify TeamCity installationLocate the TeamCity server in your environment and determine the installation path. Common locations include /opt/teamcity, C:\TeamCity, or check running services for TeamCity processes.Affected if TeamCity is present in the environment and has not been patched to version 2024.03 or later.
-
Determine installed TeamCity versionAccess the TeamCity administration interface and navigate to the 'About' page, or check the buildServer.properties file in the TeamCity data directory for the version number.Affected if The installed version is earlier than 2024.03 (for example, 2023.11, 2023.05, etc.).
-
Check if 2FA is enabledIn TeamCity administration, navigate to Authentication settings and inspect whether two-factor authentication has been configured for any user accounts or global security settings.Affected if 2FA is enabled and the TeamCity version is earlier than 2024.03, making the environment vulnerable to the bypass.
-
Review authentication logs for suspicious access patternsExamine TeamCity server logs (under /logs directory) for authentication events that may indicate attempts to bypass 2FA, looking for requests with unusual URL parameters around authentication endpoints.Affected if Unusual authentication patterns are found and the version is below 2024.03.
You are affected if TeamCity is running and the installed version is earlier than 2024.03 while 2FA authentication is enabled.
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 JetBrains TeamCity to version 2024.03 or later to patch the 2FA bypass vulnerability. After upgrading, verify that 2FA protection is functioning correctly for all configured users.
TeamCity 2024.03 or later
- Back up your current TeamCity installation, including the database and configuration files
- Download TeamCity version 2024.03 or later from the official JetBrains website (www.jetbrains.com)
- Stop the TeamCity server
- Follow the official TeamCity upgrade instructions from JetBrains documentation
- Start the TeamCity server after upgrade completes
- Verify that Two-Factor Authentication is functioning correctly after the upgrade
- Confirm the vulnerability is remediated by testing 2FA with the previously vulnerable URL parameter method
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-31136 — 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-31136 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