CVE-2024-36363
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 2022.04.7, 2022.10.6, 2023.05.6, 2023.11.5 several Stored XSS in code inspection reports were possible
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 confidenceMultiple Stored XSS vulnerabilities existed in JetBrains TeamCity's code inspection reports functionality. Attackers could inject malicious JavaScript payloads into code inspection report data, which would then be executed in the browsers of other users viewing those reports. The vulnerable code failed to properly sanitize user-supplied content displayed in inspection report outputs.
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< 2022.04.7>= 2022.10, < 2022.10.6>= 2023.05, < 2023.05.6>= 2023.11, < 2023.11.5CVSS 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.
-
Determine installed TeamCity versionAccess TeamCity Administration > Server Administration > Server Information page, or call the REST API endpoint /app/rest/server/version, or check the <TeamCity home>/logs/teamcity-version.log fileAffected if The installed version falls into any of these ranges: < 2022.04.7, >= 2022.10 but < 2022.10.6, >= 2023.05 but < 2023.05.6, >= 2023.11 but < 2023.11.5
-
Verify if code inspection reports feature is usedCheck build configurations for inspection runners (such as IntelliJ IDEA inspections, ReSharper, or other inspection tools) in the Build Features section of your build configurationsAffected if Any build configuration has code inspection runners enabled and produces inspection reports
-
Review inspection report viewing accessCheck which users have permission to view code inspection reports by examining the 'View inspection reports' permission under Administration > User Management > RolesAffected if Multiple users or external users have access to view inspection reports, increasing exposure to potential XSS
-
Inspect stored inspection report data for suspicious contentQuery the build metadata or inspect the .inspection report files in the build artifacts directory under <TeamCity Data Directory>/system/artifacts for unexpected script tags or javascript: URLsAffected if Inspection report data contains unsanitized user-controlled content that could include script tags or event handlers
You are affected if your TeamCity version is below 2022.04.7, between 2022.10-2022.10.5, between 2023.05-2023.05.5, or between 2023.11-2023.11.4 AND you use code inspection reports that could contain malicious payloads from untrusted sources.
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 · scoped2022.04.72022.10.62023.05.6
Upgrade TeamCity to version 2022.04.7, 2022.10.6, 2023.05.6, or 2023.11.5 or later to obtain the patches for these stored XSS vulnerabilities in code inspection reports.
2023.11.5 (or later stable release)
- Backup your TeamCity data and configuration before proceeding
- Stop the TeamCity server
- Download the fixed version (2023.11.5 or later from www.jetbrains.com/teamcity)
- Run the installer or apply the upgrade to your existing installation
- Start the TeamCity server
- Verify the upgrade was successful and test code inspection report functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36363 — 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-36363 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