Note:
This project will be discontinued after December 13, 2021. [more]
Product:
Teamcity
(Jetbrains)Repositories |
Unknown: This might be proprietary software. |
#Vulnerabilities | 197 |
Date | Id | Summary | Products | Score | Patch | Annotated |
---|---|---|---|---|---|---|
2020-04-22 | CVE-2020-11688 | In JetBrains TeamCity before 2019.2.1, the application state is kept alive after a user ends his session. | Teamcity | N/A | ||
2020-04-22 | CVE-2020-11687 | In JetBrains TeamCity before 2019.2.2, password values were shown in an unmasked format on several pages. | Teamcity | N/A | ||
2019-10-01 | CVE-2019-15039 | An issue was discovered in JetBrains TeamCity 2018.2.4. It had a possible remote code execution issue. This was fixed in TeamCity 2019.1. | Teamcity | N/A | ||
2019-10-31 | CVE-2019-18365 | In JetBrains TeamCity before 2019.1.4, reverse tabnabbing was possible on several pages. | Teamcity | N/A | ||
2019-10-31 | CVE-2019-18367 | In JetBrains TeamCity before 2019.1.2, a non-destructive operation could be performed by a user without the corresponding permissions. | Teamcity | N/A | ||
2019-10-31 | CVE-2019-18366 | In JetBrains TeamCity before 2019.1.2, secure values could be exposed to users with the "View build runtime parameters and data" permission. | Teamcity | N/A | ||
2019-10-31 | CVE-2019-18364 | In JetBrains TeamCity before 2019.1.4, insecure Java Deserialization could potentially allow remote code execution. | Teamcity | N/A | ||
2019-10-01 | CVE-2019-15042 | An issue was discovered in JetBrains TeamCity 2018.2.4. It had no SSL certificate validation for some external https connections. This was fixed in TeamCity 2019.1. | Teamcity | N/A | ||
2019-10-01 | CVE-2019-15038 | An issue was discovered in JetBrains TeamCity 2018.2.4. The TeamCity server was not using some security-related HTTP headers. The issue was fixed in TeamCity 2019.1. | Teamcity | N/A | ||
2019-10-02 | CVE-2019-15037 | An issue was discovered in JetBrains TeamCity 2018.2.4. It had several XSS vulnerabilities on the settings pages. The issues were fixed in TeamCity 2019.1. | Teamcity | N/A |