CVE-2024-36368
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 reflected XSS via OAuth provider configuration 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 confidenceReflected XSS vulnerability in TeamCity's OAuth provider configuration allows attackers to inject malicious scripts through OAuth settings pages. User-supplied input in the OAuth provider configuration is not properly sanitized, enabling script execution in the context of the victim's browser.
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.
-
Identify TeamCity server versionLog into TeamCity as administrator, navigate to Administration > Server Administration > Server Information page, or check the version.txt file in the <TeamCity data directory>/config directoryAffected if The displayed version number falls into any of these ranges: < 2022.04.7, >= 2022.10 but < 2022.10.6, >= 2023.05 but < 2023.05.6, or >= 2023.11 but < 2023.11.5
-
Verify OAuth provider is configuredNavigate to Administration > Authentication > OAuth Providers (or Authentication Settings) in the TeamCity web interface to see if any OAuth providers are enabled and configuredAffected if One or more OAuth providers (such as GitHub, Google, GitLab, or custom OAuth2) are added and enabled on the server
-
Confirm XSS payload delivery vector existsExamine the OAuth provider settings pages by accessing the configuration form for each enabled OAuth provider; the vulnerability exists in the input fields where OAuth client ID, client secret, or custom parameters are storedAffected if The TeamCity version is affected AND the OAuth provider configuration page accepts and saves user-supplied values without visible sanitization or encoding in the response
You are affected if your TeamCity server version is less than 2022.04.7, between 2022.10-2022.10.5, between 2023.05-2023.05.5, or between 2023.11-2023.11.4, AND you have OAuth providers configured on your server.
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 security fix. Validate that OAuth authentication continues to function correctly after the upgrade.
2023.11.5 (or latest stable 2023.11.x release)
- 1. Identify current TeamCity version by navigating to Administration > Global Settings
- 2. Based on current version, determine target upgrade version: if < 2022.04, upgrade to 2022.04.7 or later; if >= 2022.10 and < 2022.10.6, upgrade to 2022.10.6; if >= 2023.05 and < 2023.05.6, upgrade to 2023.05.6; if >= 2023.11 and < 2023.11.5, upgrade to 2023.11.5
- 3. Back up the TeamCity database and configuration files before upgrading
- 4. Download the target fixed version from www.jetbrains.com/teamcity/download/
- 5. Stop the TeamCity server
- 6. Install the upgrade following standard TeamCity upgrade documentation
- 7. Start the TeamCity server and verify all services are running
- 8. Verify the OAuth provider configuration page is accessible and functions correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.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 $4,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36368 — 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-36368 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