CVE-2024-36378
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.2 server was susceptible to DoS attacks with incorrect auth tokens
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 servers before version 2024.03.2 are vulnerable to denial-of-service attacks via malformed or incorrect authentication tokens. The server fails to properly handle invalid auth tokens, allowing attackers to crash or overwhelm the service without authentication.
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.03.2CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Determine installed TeamCity versionAccess the TeamCity web interface and navigate to Administration > Server Administration, or check the buildServer.properties file in the TeamCity data directory for the version numberAffected if The installed version is earlier than 2024.03.2
-
Verify TeamCity server is running and accessibleConfirm the TeamCity web interface is reachable over HTTP/HTTPS. The DoS vulnerability is triggered by sending malformed authentication requests to the serverAffected if The server is online and accessible to network attackers
-
Confirm authentication endpoints are exposedCheck that the /ajax.html?test=... or similar authentication-related endpoints are reachable without authentication. These are the paths where malformed tokens can trigger the DoSAffected if Unauthenticated access to authentication endpoints is permitted
If your TeamCity version is below 2024.03.2 and the server is accessible over the network, you are potentially affected by this denial-of-service vulnerability via malformed auth tokens.
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.2
Upgrade TeamCity to version 2024.03.2 or later to patch the vulnerability. Consider implementing rate limiting on authentication endpoints as an additional safeguard.
2024.03.2
- 1. Back up your TeamCity data directory (typically <TeamCity Data Directory>) and database before upgrading
- 2. Download TeamCity 2024.03.2 from the official JetBrains website (www.jetbrains.com/teamcity/download)
- 3. Stop the TeamCity server gracefully
- 4. Install the new TeamCity 2024.03.2 distribution following the standard upgrade procedure
- 5. Start the TeamCity server
- 6. Verify the server is running and accessible
- 7. Confirm the version shows 2024.03.2 in the administration UI under "About"
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-36378 — 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-36378 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