Loading vulnerability…
Gitlist versions prior to 0.5.0 are vulnerable to command injection via shell metacharacters in file names passed through the URI to the blame, file, or stats pages. The application fails to properly sanitize user-supplied input in the file name parameter, allowing attackers to inject arbitrary shell commands that are executed on the server.
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 (1 hidden).
This repository contains a single Metasploit module (modules/exploits/linux/http/gitlist_exec.rb) that exploits an unauthenticated remote command execution vulnerability (CVE-2014-4511) in Gitlist version 0.4.0. The exploit leverages improper handling of file names in the blame functionality, allowing arbitrary shell command execution via a crafted HTTP request. The module is weaponized, supporting customizable command payloads and various interpreters (e.g., bash, python, perl, netcat). The attacker does not need authentication and only requires access to the vulnerable Gitlist instance. The main endpoints targeted are the root path (for repository enumeration) and the blame path (for command injection). The code is written in Ruby and is structured as a standard Metasploit exploit module, making it easy to use within the Metasploit framework.
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.