Script execution via stored build-log content
Published Jul 12, 2023 · Updated Oct 22, 2024
Stored cross-site scripting in JetBrains TeamCity before 2023.05.1 allows remote authenticated users to execute script through build logs. JetBrains identifies build-log viewing as the execution locus but has not disclosed which log-producing path stores attacker-controlled content without safe output encoding. Exploitation requires a user to view the affected log, and the resulting code runs only in that viewer's browser context.
Summary
What happened
Stored cross-site scripting in JetBrains TeamCity before 2023.05.1 allows remote authenticated users to execute script through build logs. JetBrains identifies build-log viewing as the execution locus but has not disclosed which log-producing path stores attacker-controlled content without safe output encoding. Exploitation requires a user to view the affected log, and the resulting code runs only in that viewer's browser context.
The record
- CVE
- CVE-2023-38065
- Published
- Jul 12, 2023
- Updated
- Oct 22, 2024
- Vendor
- JetBrains
- Product
- TeamCity
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 12, 2023CVE publishedPublication date reported by the CVE source.
- Oct 22, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2023.05.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo