Skip to main content
VulnerabilityPublished Updated

CVE-2024-37051: JetBrains IntelliJ IDEA · Insufficiently Protected Credentials

Affects JetBrains IntelliJ IDEASource CVE Database V5

0
Compare

Public exploit available · CVSS 9.3 Critical · fixed in 2024.2 EAP3 : patch JetBrains IntelliJ IDEA as a priority.

Data as of 4 Nov 2026, 00:13 UTC

CVSS 3.1 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (JetBrains)CVSS 3.19.3
EPSS
4.8% chance of exploitation in 30 days – higher than 92% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
Proof of concept is public or traded
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2024-09-17.

Patch
Available – fixed in 2024.2 EAP3, 2024.1.3, 2023.3.7 +18
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 10 Jun 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CISA SSVC: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by JetBrains s.r.o.

    , 10 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. CISA SSVC assessment

    proof of concept public

    , 99 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA SSVC, the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
JetBrainsIntelliJ IDEAAffected
  • >=2023.1 <2023.1.7
  • >=2023.1 <2023.2.7
  • >=2023.1 <2023.3.7
  • >=2023.1 <2024.1.3
  • =2023.1
Fixed in
  • 2024.2 EAP3
  • 2024.1.3
  • 2023.3.7
  • 2023.2.7
  • 2023.1.7
JetBrainsAquaAffected
  • <2024.1.2
Fixed in
  • 2024.1.2
JetBrainsCLionAffected
  • >=2023.1 <2023.1.7
  • >=2023.1 <2023.2.4
  • >=2023.1 <2023.3.5
  • >=2023.1 <2024.1.3
  • =2023.1
Fixed in
  • 2024.2 EAP2
  • 2024.1.3
  • 2023.3.5
  • 2023.2.4
  • 2023.1.7
JetBrainsDataGripAffected
  • >=2023.1 <2024.1.4
Fixed in
  • 2024.1.4
JetBrainsDataGripAffected
  • >=2023.1 <2023.3.5
Fixed in
  • 2023.3.5
JetBrainsDataGripAffected
  • >=2023.1 <2023.2.4
Fixed in
  • 2023.2.4

AI-suggested

JetBrains has released official fixes for this vulnerability in multiple versions including 2023.1.7, 2023.2.7, 2023.3.7, 2024.1.3, 2024.1.2, 2024.1.4, and 2024.2 EAP releases. Users and organizations should upgrade affected JetBrains IDEs to these fixed versions to mitigate the risk. No additional mitigation steps are indicated beyond applying the official patches.

Description

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

References

Community reviews

Loading reviews…