dbcve.org
AquaApplication · Jetbrains

CVE-2024-37051

HIGH · 7.5 CVSS v3.1 Published 2024-06-10
Fix available
A fix is available. Upgrade to 2023.1.3 / 2023.1.6 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

GitHub access tokens stored in JetBrains IDEs were being leaked to third-party sites. The IDEs were likely including authentication credentials in HTTP requests (headers, query parameters, or referrer fields) when making outbound connections to non-GitHub domains, exposing tokens intended solely for GitHub API authentication.

MitigationUpdate all affected JetBrains IDE installations to the patched versions specified in the advisory. Additionally, revoke and regenerate any GitHub access tokens that may have been used with these IDE versions as they may be compromised.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AquaApplication
Affected:< 2024.1.2
ClionApplication
Affected:< 2023.1.7>= 2023.2.0, < 2023.2.4>= 2023.3.0, < 2023.3.5>= 2024.1.0, < 2024.1.3
DatagripApplication
Affected:>= 2023.1.0, < 2023.1.3>= 2023.2.0, < 2023.2.4>= 2023.3.0, < 2023.3.5>= 2024.1.0, < 2024.1.4
DataspellApplication
Affected:< 2023.1.6>= 2023.2.0, < 2023.2.7>= 2023.3.0, < 2023.3.6>= 2024.1.0, < 2024.1.2
GolandApplication
Affected:< 2023.1.6>= 2023.2.0, < 2023.2.7>= 2023.3.0, < 2023.3.7>= 2024.1.0, < 2024.1.3
Intellij IdeaApplication
Affected:< 2023.1.7>= 2023.2.0, < 2023.2.7>= 2023.3.0, < 2023.3.7>= 2024.1.0, < 2024.1.3
MpsApplication
Affected:< 2023.2.1= 2023.3.0
PhpstormApplication
Affected:< 2023.1.6>= 2023.2.0, < 2023.2.6>= 2023.3.0, < 2023.3.7>= 2024.1.0, < 2024.1.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed JetBrains IDE product and version
    Open the IDE, go to Help → About and note the product name and exact version number (e.g., IntelliJ IDEA 2023.2.5)
    Affected if The installed version falls within any of the affected ranges for that product
  2. Confirm GitHub token authentication is configured
    In the IDE, go to Settings → Version Control → GitHub and check if any GitHub accounts or personal access tokens are linked
    Affected if A GitHub account or token is added and the IDE version is vulnerable
  3. Check for recent outbound HTTP requests to non-GitHub domains
    Review IDE logs, network traffic logs, or proxy logs for HTTP requests that include GitHub tokens in headers, query parameters, or referrer fields going to non-github.com domains
    Affected if Any such requests are found in logs or traffic captures

You are affected if you use any of the listed JetBrains IDEs at a version within the specified ranges and have GitHub tokens configured in the IDE, as the token may have been leaked to third-party sites.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2023.1.3 / 2023.1.6 / 2023.1.7 or later
Fixed in 2023.1.32023.1.62023.1.7
Interim mitigation

Update all affected JetBrains IDE installations to the patched versions specified in the advisory. Additionally, revoke and regenerate any GitHub access tokens that may have been used with these IDE versions as they may be compromised.

Recommended fix High confidence

Upgrade to the fixed version for your product: Aqua 2024.1.2+, CLion 2023.1.7+/2023.2.4+/2023.3.5+/2024.1.3+, 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+, GoLand 2023.1.6+/2023.2.7+/2023.3.7+/2024.1.3+, IntelliJ IDEA 2023.1.7+/2023.2.7+/2023.3.

  1. 1. Identify the JetBrains IDE product and current version in use (Help > About)
  2. 2. Determine if the current version falls within the affected version ranges listed for the specific product
  3. 3. If affected, download the fixed version from the official JetBrains website (www.jetbrains.com) or use the JetBrains Toolbox app
  4. 4. Install the fixed version which includes the patch for CVE-2024-37051
  5. 5. After upgrading, verify that GitHub access tokens are no longer exposed to third-party sites by reviewing the IDE's GitHub authentication settings
  6. 6. Consider rotating any GitHub access tokens that may have been used in the affected versions as a precautionary measure

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Aqua Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-37051 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-37051 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data