CVE-2024-37051: Critical severity jetbrains aqua vulnerability
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
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-37051?
CVE-2024-37051 is considered a serious vulnerability as it may expose sensitive GitHub access tokens to third-party sites.
How do I fix CVE-2024-37051?
To mitigate CVE-2024-37051, upgrade your JetBrains IDE to the latest versions that address this vulnerability.
Which versions of JetBrains IDEs are affected by CVE-2024-37051?
CVE-2024-37051 affects various JetBrains IDEs, specifically versions prior to 2023.1.7, 2023.2.7, 2023.3.7, and other specific versions listed in the vulnerability details.
What types of access can be compromised by CVE-2024-37051?
CVE-2024-37051 can potentially allow unauthorized third-party access to GitHub repositories due to exposed tokens.
Is CVE-2024-37051 easily exploitable?
The exploitability of CVE-2024-37051 depends on the configuration of the affected systems and the presence of the vulnerable IDE versions.