CVE-2024-41825
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.07 stored XSS was possible on the Code Inspection tab
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 confidenceStored XSS vulnerability in JetBrains TeamCity before version 2024.07 on the Code Inspection tab. User-supplied input is stored and rendered to other users without proper sanitization, allowing injection of malicious scripts.
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.07CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 versionNavigate to the TeamCity administration dashboard and locate the version information, typically found in the 'About' section or footer of the admin pages. Alternatively, check the build server logs or the 'teamcity-server.log' file for version details.Affected if The installed version is any release before 2024.07 (e.g., 2024.06, 2024.05, 2024.04, etc.)
-
Confirm Code Inspection tab is in useCheck if any project in TeamCity has code inspection features enabled or if any build configurations include static analysis tools that feed into the Code Inspection tab. Review the project settings and build configuration pages.Affected if Code Inspection tab is accessible and being used within TeamCity
-
Review user access to Code InspectionDetermine which users have permission to view or contribute to the Code Inspection tab. Check the 'Roles and Permissions' section in administration to identify users with access to this feature.Affected if Multiple users or untrusted users have access to view the Code Inspection tab
-
Audit existing entries in Code InspectionInspect the Code Inspection tab for any suspicious entries, unusual script tags, or unexpected HTML content in code inspection results. Look for patterns like '<script>', 'javascript:', 'onerror=', or other XSS vectors in displayed inspection messages.Affected if Any unexpected or unsanitized content is visible in the Code Inspection output
You are affected if your TeamCity version is before 2024.07 and the Code Inspection tab is accessible to users who could inject malicious scripts.
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.07
Upgrade to TeamCity 2024.07 or later. Alternatively, implement input validation and output encoding on the Code Inspection tab as a compensating control until upgrade is possible.
2024.07
- Backup the TeamCity server data and configuration before proceeding with the upgrade
- Download TeamCity version 2024.07 or later from the official JetBrains website (www.jetbrains.com/teamcity/download)
- Stop the TeamCity server gracefully
- Run the TeamCity installer for the new version, following the on-screen upgrade instructions
- Start the TeamCity server after the upgrade completes
- Verify that the Code Inspection tab is accessible and the XSS vulnerability is resolved by testing with the application
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-41825 — 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-41825 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