CVE-2024-36370
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 stored XSS via OAuth connection settings was 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 confidenceStored XSS vulnerability in TeamCity's OAuth connection settings allows authenticated users with OAuth configuration privileges to inject malicious JavaScript that executes when other users view the OAuth configuration pages. The vulnerability affects multiple version branches before the patched releases.
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.
-
Locate your TeamCity version numberLog into TeamCity as an administrator, click your username in the top-right corner, and select 'About TeamCity' from the dropdown menu. The version is displayed in the dialog that appears.Affected if The version shown is less than 2022.04.7, or falls between 2022.10.0-2022.10.5, 2023.05.0-2023.05.5, or 2023.11.0-2023.11.4
-
Verify if OAuth authentication is enabledNavigate to Administration > Authentication Settings and check if any OAuth-based providers (such as GitHub, GitLab, Google, etc.) are configured or enabled.Affected if OAuth providers are configured and users can access the OAuth configuration pages
-
Identify users with OAuth configuration privilegesGo to Administration > User Management > Roles and check which users or groups are assigned roles that include 'OAuth connection' or 'OAuth configuration' permissions.Affected if Multiple users or untrusted accounts have OAuth configuration permissions
-
Inspect OAuth connection settings for suspicious contentNavigate to Administration > Authentication > OAuth Settings and examine each OAuth provider's configuration fields (especially client ID, client secret, or custom endpoint fields) for unusual characters or script tags such as <script> or javascript:.Affected if Any OAuth configuration field contains encoded or raw script tags, event handlers like onload/onerror, or suspicious URL patterns
Your TeamCity is affected if the installed version falls within the vulnerable ranges AND OAuth authentication is enabled with accessible configuration pages.
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, 2023.11.5 or later to obtain the patch. Limit OAuth configuration permissions to trusted administrators until upgrade is complete.
Upgrade to TeamCity 2023.11.5 or later (latest stable release)
- 1. Back up your TeamCity data and configuration files
- 2. Review the TeamCity upgrade documentation for your current version
- 3. Download the appropriate fixed version (2023.11.5 or later) from the official JetBrains TeamCity download page
- 4. Perform a test upgrade in a non-production environment first
- 5. Execute the upgrade following JetBrains official upgrade instructions
- 6. After upgrade, verify the OAuth connection settings functionality works correctly
- 7. Test that the XSS vulnerability is remediated by attempting to inject script content in OAuth settings (in a safe, authorized test environment only)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36370 — 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-36370 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