Loading vulnerability…
CVE-2018-14912 is a directory traversal vulnerability in cgit before version 1.2.1. The cgit_clone_objects path-handling logic inadequately constrains repository object paths when HTTP cloning is enabled, allowing attacker-controlled parent-directory traversal sequences to resolve outside the intended Git repository. This can expose files accessible to the cgit service account.
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 auxiliary scanner module (modules/auxiliary/scanner/http/cgit_traversal.rb) that exploits a directory traversal vulnerability in cgit versions prior to 1.2.1 (CVE-2018-14912). The exploit targets servers with the 'enable-http-clone' configuration flag enabled (default setting). The module allows an attacker to read arbitrary files from the server's filesystem by sending a crafted HTTP GET request to the cgit service, using a traversal sequence in the 'path' parameter. The attacker can specify the file to read (default: /etc/passwd), the base URI of the cgit install, the repository name, and the traversal depth. The exploit saves the retrieved file contents as loot. The code is written in Ruby and is designed to be run within the Metasploit framework. No fake or detection-only code is present; this is a functional exploit module.
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 and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.