CVE-2024-31135
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 open redirect was possible on the login page
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 confidenceAn open redirect vulnerability existed in JetBrains TeamCity's login page prior to version 2024.03, allowing attackers to craft malicious URLs that would redirect authenticated users to arbitrary external websites after login. This occurs when the login page does not properly validate or sanitize the redirect parameter, enabling phishing attacks leveraging trusted TeamCity URLs.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed TeamCity versionCheck the TeamCity server version by navigating to Administration > Global Settings or by checking the <TeamCity home>/buildAgent/conf/buildAgent.properties file if agents are configured. Alternatively, check the About page in the TeamCity UI.Affected if The installed version is lower than 2024.03 (e.g., 2024.02, 2023.x, earlier versions).
-
Review server configuration for redirect settingsExamine the <TeamCity home>/conf/server.xml file and look for any redirect-related configuration parameters in the login module or security settings.Affected if Redirect parameters are configured to allow arbitrary external URLs or validation is disabled/missing.
-
Inspect login page response for redirect validationAccess the TeamCity login page (typically at /login.html) and inspect the HTTP response headers and form parameters, particularly any 'redirect' or 'returnUrl' parameters, to verify if external domains are accepted.Affected if The login page accepts and reflects an external URL in the redirect parameter without validation or sanitization.
-
Check authentication logs for suspicious redirect usageReview TeamCity authentication and audit logs for any login events where the redirect parameter contains external domains (non-internal URLs). Look for patterns like redirect=http:// or redirect=https://Affected if Logs show redirect parameters pointing to external domains being processed after authentication.
You are affected if your installed TeamCity version is any release prior to 2024.03 and the login page redirect parameter accepts arbitrary external URLs without proper validation.
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 remediate the open redirect vulnerability. After upgrading, verify that the login redirect functionality works correctly and does not allow unauthorized redirects.
TeamCity 2024.03
- Backup your TeamCity data and configuration before upgrading
- Download TeamCity 2024.03 (or later) from the official JetBrains website
- Stop the running TeamCity server
- Install the new version following the standard TeamCity upgrade procedure
- Start the TeamCity server and verify the login page is accessible
- Confirm the open redirect vulnerability is no longer present by testing that redirects from the login page are properly validated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-31135 — 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-31135 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