Loading vulnerability…
GitKraken GitLens versions prior to 14.0.0 contain a vulnerability in the handling of workspace trust within Visual Studio Code. An attacker can craft a malicious file that, when opened in a vulnerable version of GitLens, can trigger the execution of arbitrary code on the victim's system. The vulnerability is due to insufficient validation or sanitization of files processed by the workspace trust component.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (gitlens_local_config_exec.rb) that exploits CVE-2023-46944, a vulnerability in the GitLens extension for Visual Studio Code (prior to v14.0.0). The exploit works by generating a malicious zip archive (repo.zip) that mimics a git repository, including a .git/config file with a specially crafted 'fsmonitor' directive containing a Metasploit payload. When a victim opens this repository in VSCode with the vulnerable GitLens extension, arbitrary code execution is triggered. The module supports both Linux/Unix and Windows targets, delivering payloads appropriate to the platform. The exploit is operational and leverages local file-based attack vectors, with the main fingerprintable endpoints being the .git/config file and the malicious zip archive. The repository is structured as a standard Metasploit exploit module, with all logic contained in a single Ruby file.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.