Monday, January 13, 2025
HomeCVE/vulnerabilityJetBrains Warns of GitHub Plugin that Exposes Access Tokens

JetBrains Warns of GitHub Plugin that Exposes Access Tokens

Published on

A critical vulnerability (CVE-2024-37051) in the JetBrains GitHub plugin for IntelliJ-based IDEs (2023.1 and later) exposed access tokens to malicious content within GitHub pull requests, allowing attackers to steal tokens and potentially compromise linked accounts, even with two-factor authentication enabled. 

JetBrains has addressed the issue with a patch and collaborated with GitHub on mitigation efforts.

Users are advised to update their IDEs and consider revoking any GitHub tokens used by the plugin. 

They have provided available fixed versions for JetBrains IDEs as of today, while Aqua currently has a single fixed version available, 2024.1.2.

With ANYRUN You can Analyze any URL, Files & Email for Malicious Activity : Start your Analysis

CLion offers multiple fixed versions, spanning from 2023.1.7 all the way up to the latest Early Access Program (EAP) build, 2024.2 EAP2. DataGrip and DataSpell each have a fixed version from the current year (2024.1.4 and 2024.1.2, respectively). 

GoLand and IntelliJ IDEA users benefit from a wider range of fixed versions, including those from 2023 and the current EAP builds for 2024.2.

Finally, MPS offers fixed versions starting in the middle of 2023 (2023.2.1), with the latest being an EAP build from the current year (2024.1 EAP2).  

A security vulnerability in the JetBrains GitHub plugin that could expose access tokens has been patched, which affects all IntelliJ-based IDEs (including PhpStorm, PyCharm, Rider, RubyMine, WebStorm, and RustRover) from version 2023.1 onwards. 

The JetBrains GitHub plugin has been updated with the fix, and insecure versions have been removed from the JetBrains Marketplace.

Users are strongly recommended to update the plugin to the latest version immediately. 

An external security report submitted on May 29, 2024, identified a vulnerability (CVE-2024-37051) in the JetBrains GitHub plugin for IntelliJ-based IDEs (version 2023.1 and later). 

The vulnerability could expose a user’s GitHub access token to a malicious third-party if a pull request containing malicious content is handled by the IDE, while updating to the latest IDE version is strongly recommended to mitigate this vulnerability. 

JetBrains identified a security vulnerability in their GitHub plugin for IntelliJ-based IDEs (versions 2023.1 and later) that could expose access tokens, and to mitigate this issue, they contacted GitHub and implemented measures that might cause the plugin to malfunction in older IDE versions. 

While a permanent fix is underway, updating the plugin and IDE to the latest versions is crucial to ensuring security and full functionality. 

To ensure compatibility and security when using the JetBrains IDE GitHub integration plugin, update to the latest IDE version, and if you’ve used the plugin’s pull request features, revoke any associated GitHub tokens. 

The plugin might use OAuth or Personal Access Tokens (PATs). Revoke them through GitHub’s application settings or token management page.

Note that revoking tokens disables all plugin features, including Git operations, requiring reconfiguration.

Looking for Full Data Breach Protection? Try Cynet's All-in-One Cybersecurity Platform for MSPs: Try Free Demo 

Latest articles

Critical macOS Vulnerability Lets Hackers to Bypass Apple’s System Integrity Protection

Microsoft Threat Intelligence has uncovered a critical macOS vulnerability that allowed attackers to bypass...

CISA Released A Free Guide to Enhance OT Product Security

To address rising cyber threats targeting critical infrastructure, the U.S. Cybersecurity and Infrastructure Security...

Microsoft Warns of MFA Issue Affecting Microsoft 365 users

Microsoft has issued a warning regarding an ongoing issue with Multi-Factor Authentication (MFA) that...

RedCurl APT Deploys Malware via Windows Scheduled Tasks Exploitation

Researchers identified RedCurl APT group activity in Canada in late 2024, where the attackers...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

Critical macOS Vulnerability Lets Hackers to Bypass Apple’s System Integrity Protection

Microsoft Threat Intelligence has uncovered a critical macOS vulnerability that allowed attackers to bypass...

CISA Released A Free Guide to Enhance OT Product Security

To address rising cyber threats targeting critical infrastructure, the U.S. Cybersecurity and Infrastructure Security...

Microsoft Warns of MFA Issue Affecting Microsoft 365 users

Microsoft has issued a warning regarding an ongoing issue with Multi-Factor Authentication (MFA) that...