This article is a part of our Vulnerability Database (back to index)
Cross-site Scripting occurrences in Youtrack
In JetBrains YouTrack before 2022.1.43563 HTML code from the issue description was being rendered (2022-04-05, CVE-2022-28648)
In JetBrains YouTrack before 2022.1.43700 it was possible to inject JavaScript into Markdown in the YouTrack Classic UI (2022-04-05, CVE-2022-28650)
JetBrains YouTrack before 2021.4.31698 was vulnerable to stored XSS on the Notification templates page. (2022-02-25, CVE-2022-24344)
JetBrains YouTrack before 2021.4.36872 was vulnerable to stored XSS via a project icon. (2022-02-25, CVE-2022-24347)
In JetBrains YouTrack before 2021.3.21051, stored XSS is possible. (2021-11-09, CVE-2021-43184)
JetBrains YouTrack before 2021.3.24402 is vulnerable to stored XSS. (2021-11-09, CVE-2021-43186)
In JetBrains YouTrack before 2021.2.17925, stored XSS was possible. (2021-08-06, CVE-2021-37552)
In JetBrains YouTrack before 2020.6.6441, stored XSS was possible via an issue attachment. (2021-05-11, CVE-2021-27733)
In JetBrains YouTrack before 2021.1.9819, a pull request's title was sanitized insufficiently, leading to XSS. (2021-05-11, CVE-2021-31903)
JetBrains YouTrack 2019.2 before 2019.2.59309 was vulnerable to XSS via an issue description. (2020-01-30, CVE-2020-7913)
In JetBrains YouTrack through 2019.2.56594, stored XSS was found on the issue page. (2019-10-02, CVE-2019-16171)
JetBrains YouTrack versions before 2019.1.52584 had a possible XSS in the issue titles. (2019-10-01, CVE-2019-14952)
Why Cross-site Scripting can be dangerous
Cross site scripting is an attack where a web page executes code that is injected by an adversary. It usually appears, when users input is presented. This attack can be used to impersonate a user, take over control of the session, or even steal API keys.
The attack can be executed e.g. when you application injects the request parameter directly into the HTML code of the page returned to the user:
https://server.com/confirmation?message=Transaction+Complete
what results in:
<span>Confirmation: Transaction Complete</span>
In that case the message can be modified to become a valid Javascript code, e.g.:
https://server.com/confirmation?message=<script>dangerous javascript code here</script>
and it will be executed locally by the user's browser with full access to the user's personal application/browser data:
<span>Confirmation: <script>dangerous javascript code here</script></span>