Cyber Resilience

CVE-2023-34220

XSS in Jetbrains Teamcity ≤ 2023.05

High EPSSXSS
Published
31 May 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 4.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
EPSS Score 0.61 99.1th percentile
Risk Priority 70 floored blend · peak EPSS

Summary

CVE-2023-34220 is a medium-severity Cross-site Scripting (CWE-79) vulnerability in Jetbrains Teamcity. Its CVSS base score is 4.6 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Browser Session Hijacking (T1185); ranked in the top 0.9% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2023-34220 is a stored cross-site scripting vulnerability (CWE-79) affecting the Commit Status Publisher window in JetBrains TeamCity versions prior to 2023.05. The flaw carries a CVSS 3.1 score of 4.6 and permits injection of persistent scripts that execute in the context of other users viewing the affected component.

An attacker with low-privileged authenticated access can supply malicious input through the Commit Status Publisher feature; when another user subsequently views the window, the script runs with that user's permissions, enabling limited data exposure or actions within the TeamCity interface.

JetBrains addressed the issue in the 2023.05 release, as documented on its privacy and security fixes page. The associated EPSS score rose from a low baseline to a peak of 0.0772 on 2025-12-11 before receding to the current value of 0.0091, indicating a period of increased exploitation interest after disclosure.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

In JetBrains TeamCity before 2023.05 stored XSS in the Commit Status Publisher window was possible

CWE(s)
CWE-79

Related Threats

MITRE ATT&CK Enterprise Techniques

T1185 Browser Session Hijacking Collection
Adversaries may take advantage of security vulnerabilities and inherent functionality in browser software to change content, modify user-behaviors, and intercept information as part of various browser session hijacking techniques.
attack.mitre.org →
T1539 Steal Web Session Cookie Credential Access
An adversary may steal web application or service session cookies and use them to gain access to web applications or Internet services as an authenticated user without needing credentials.
attack.mitre.org →
T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-34221Same product: Jetbrains Teamcity
CVE-2023-38065Same product: Jetbrains Teamcity
CVE-2023-34229Same product: Jetbrains Teamcity
CVE-2023-41248Same product: Jetbrains Teamcity
CVE-2023-38063Same product: Jetbrains Teamcity
CVE-2023-38066Same product: Jetbrains Teamcity
CVE-2023-41249Same product: Jetbrains Teamcity
CVE-2023-43566Same product: Jetbrains Teamcity
CVE-2023-34226Same product: Jetbrains Teamcity
CVE-2023-41250Same product: Jetbrains Teamcity

Affected Assets

jetbrains
teamcity
≤ 2023.05

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.1.2
  • V1.3.2

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

CA-8 Penetration Testing
addresses: CWE-79

Penetration testing submits XSS payloads to web applications, detecting cross-site scripting flaws for subsequent remediation.

SI-10 Information Input Validation
addresses: CWE-79

Validates web inputs to reject script-related content that could produce XSS.

SI-15 Information Output Filtering
addresses: CWE-79

Output validation against expected content can reject or sanitize script content in generated web pages, reducing XSS exploitability.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly target introduction of XSS via coding standards/testing (mostly), yet the single broad outcome leaves many specific neutralization vectors unaddressed (partial).

PR.PS-02 partial match
prevents

Patching and EOL replacement can remediate known XSS instances in libraries or frameworks (partial) but do nothing to enforce input neutralization in application code (none).

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Secure-coding testing and automated code-analysis tools are applied to detect improper neutralization of script-related content during web-page generation.

A.5.6 Contact with special interest groups partial match
prevents

Knowledge exchange on emerging attack techniques and patches reduces the likelihood that cross-site scripting flaws remain unaddressed in deployed applications.

A.5.7 Threat intelligence partial match
prevents

Operational indicators of compromise for web-application attacks can be incorporated into WAF or input-filtering rules, lowering the likelihood that unsanitized data reaches the browser.

A.8.25 Secure development life cycle partial match
prevents

Requiring language-specific secure-coding standards and automated scanning during the SDLC catches missing output encoding or improper neutralization of untrusted data before the software reaches production.

A.8.28 Secure coding partial match
prevents

Secure-coding standards, SAST scans and removal of insecure code samples together eliminate the failure to neutralize script content that produces cross-site scripting flaws.

A.8.7 Protection against malware none match
none

Webpage malware scanning and block-listing of known malicious sites reduce the likelihood that reflected or stored script payloads reach a user’s browser.

References