CVE-2013-10039 is a command injection vulnerability in GestioIP 3.0, affecting commit ac67be and earlier, in the ip_checkhost.cgi component. The flaw is triggered by crafted input supplied to the 'ip' parameter, which is insufficiently sanitized before being incorporated into a shell command. An attacker can embed a base64-encoded payload in this parameter to cause arbitrary shell command execution on the underlying server. Depending on how GestioIP is deployed, exploitation may require authentication.
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 (gestioip_exec.rb) that exploits a command injection vulnerability (CVE-2013-10039) in GestioIP version 3.0. The exploit targets the 'ip_checkhost.cgi' endpoint, which is accessible under the '/gestioip/' URI. The module can operate with or without authentication, depending on the target's configuration. If authentication is required, valid credentials must be supplied. The exploit works by sending a specially crafted HTTP GET request to the vulnerable CGI script, injecting a base64-encoded payload that is written to a temporary file and then executed, resulting in arbitrary command execution on the target system. The payload is customizable via the Metasploit framework and is executed with the privileges of the web server user. The repository is structured as a typical Metasploit module and is written in Ruby.
2 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.