Loading vulnerability…
In gitlab-shell before 1.7.3, as used in GitLab 5.0 before 5.4.1 and 6.x before 6.2.3, the SSH key upload feature (lib/gitlab_keys.rb) fails to properly sanitize input, allowing remote authenticated users to inject shell metacharacters into their uploaded public key. This results in arbitrary command execution on the server under the context in which gitlab-shell is running.
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 (gitlab_shell_exec.rb) that exploits a command injection vulnerability (CVE-2013-4490) in Gitlab-shell versions prior to 1.7.4. The exploit targets the SSH key addition functionality, where the provided SSH key is unsafely used in a system call, allowing an attacker to inject arbitrary commands. The module requires valid Gitlab user credentials to authenticate and then injects a malicious SSH key containing the payload. The exploit supports multiple payload types (command, staged, python) and targets Linux/Unix platforms. The main endpoints targeted are the Gitlab login page and the SSH key management endpoints. The code is operational and can deliver arbitrary payloads, but is not weaponized for mass exploitation as it requires valid credentials and some manual configuration.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.