JetBrains PyCharm 2016.1.5

CPE Details

JetBrains PyCharm 2016.1.5
2016.1.5
2019-10-07
10h42 +00:00
2019-10-07
10h42 +00:00
Alerte pour un CPE
Restez informé de toutes modifications pour un CPE spécifique.
Gestion des notifications

CPE Name: cpe:2.3:a:jetbrains:pycharm:2016.1.5:*:*:*:*:*:*:*

Informations

Vendor

jetbrains

Product

pycharm

Version

2016.1.5

Related CVE

Open and find in CVE List

CVE ID Publié Description Score Gravité
CVE-2024-37051 2024-06-10 15h58 +00:00 GitHub access token could be exposed to third-party sites in JetBrains IDEs after version 2023.1 and less than: IntelliJ IDEA 2023.1.7, 2023.2.7, 2023.3.7, 2024.1.3, 2024.2 EAP3; Aqua 2024.1.2; CLion 2023.1.7, 2023.2.4, 2023.3.5, 2024.1.3, 2024.2 EAP2; DataGrip 2023.1.3, 2023.2.4, 2023.3.5, 2024.1.4; DataSpell 2023.1.6, 2023.2.7, 2023.3.6, 2024.1.2, 2024.2 EAP1; GoLand 2023.1.6, 2023.2.7, 2023.3.7, 2024.1.3, 2024.2 EAP3; MPS 2023.2.1, 2023.3.1, 2024.1 EAP2; PhpStorm 2023.1.6, 2023.2.6, 2023.3.7, 2024.1.3, 2024.2 EAP3; PyCharm 2023.1.6, 2023.2.7, 2023.3.6, 2024.1.3, 2024.2 EAP2; Rider 2023.1.7, 2023.2.5, 2023.3.6, 2024.1.3; RubyMine 2023.1.7, 2023.2.7, 2023.3.7, 2024.1.3, 2024.2 EAP4; RustRover 2024.1.1; WebStorm 2023.1.6, 2023.2.7, 2023.3.7, 2024.1.4
9.3
Critique
CVE-2022-29821 2022-04-28 07h55 +00:00 In JetBrains Rider before 2022.1 local code execution via links in ReSharper Quick Documentation was possible
7.7
Haute
CVE-2022-29820 2022-04-28 07h55 +00:00 In JetBrains PyCharm before 2022.1 exposure of the debugger port to the internal network was possible
3.5
Bas
CVE-2021-30005 2021-05-11 09h42 +00:00 In JetBrains PyCharm before 2020.3.4, local code execution was possible because of insufficient checks when getting the project from VCS.
7.8
Haute
CVE-2019-14958 2019-10-02 16h40 +00:00 JetBrains PyCharm before 2019.2 was allocating a buffer of unknown size for one of the connection processes. In a very specific situation, it could lead to a remote invocation of an OOM error message because of Uncontrolled Memory Allocation.
7.5
Haute