Show filters
456 Total Results
Displaying 191-200 of 456
Sort by:
Attacker Value
Unknown
CVE-2022-36321
Disclosure Date: July 20, 2022 (last updated February 24, 2025)
In JetBrains TeamCity before 2022.04.2 the private SSH key could be written to the build log in some cases
0
Attacker Value
Unknown
CVE-2022-34894
Disclosure Date: July 01, 2022 (last updated February 24, 2025)
In JetBrains Hub before 2022.2.14799, insufficient access control allowed the hijacking of untrusted services
0
Attacker Value
Unknown
CVE-2022-29930
Disclosure Date: May 12, 2022 (last updated February 23, 2025)
SHA1 implementation in JetBrains Ktor Native 2.0.0 was returning the same value. The issue was fixed in Ktor version 2.0.1.
0
Attacker Value
Unknown
CVE-2022-29929
Disclosure Date: May 12, 2022 (last updated February 23, 2025)
In JetBrains TeamCity before 2022.04 potential XSS via Referrer header was possible
0
Attacker Value
Unknown
CVE-2022-29928
Disclosure Date: May 12, 2022 (last updated February 23, 2025)
In JetBrains TeamCity before 2022.04 leak of secrets in TeamCity agent logs was possible
0
Attacker Value
Unknown
CVE-2022-29927
Disclosure Date: May 12, 2022 (last updated February 23, 2025)
In JetBrains TeamCity before 2022.04 reflected XSS on the Build Chain Status page was possible
0
Attacker Value
Unknown
CVE-2022-29821
Disclosure Date: April 28, 2022 (last updated February 23, 2025)
In JetBrains Rider before 2022.1 local code execution via links in ReSharper Quick Documentation was possible
0
Attacker Value
Unknown
CVE-2022-29820
Disclosure Date: April 28, 2022 (last updated February 23, 2025)
In JetBrains PyCharm before 2022.1 exposure of the debugger port to the internal network was possible
0
Attacker Value
Unknown
CVE-2022-29819
Disclosure Date: April 28, 2022 (last updated February 23, 2025)
In JetBrains IntelliJ IDEA before 2022.1 local code execution via links in Quick Documentation was possible
0
Attacker Value
Unknown
CVE-2022-29818
Disclosure Date: April 28, 2022 (last updated February 23, 2025)
In JetBrains IntelliJ IDEA before 2022.1 origin checks in the internal web server were flawed
0
