CVE-2013-6829 is a command injection vulnerability in PineApp Mail-SeCure, specifically in the admin/confnetworking.html interface. The vulnerability arises because the pinghost parameter, used during a ping operation, does not properly sanitize input, allowing remote attackers to inject arbitrary shell metacharacters. This enables execution of arbitrary commands on the underlying system with the privileges of the web server process.
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/pineapp_test_li_conn_exec.rb) targeting a command injection vulnerability (CVE-2013-6829) in PineApp Mail-SeCure 3.70. The exploit abuses the /admin/test_li_connection.php endpoint, which insecurely passes user input to the system() PHP function. The module first retrieves a session cookie by sending a GET request with specific parameters, then exploits the vulnerability by injecting a semicolon and arbitrary command into the 'iptest' parameter. The exploit is operational and allows remote command execution as the web server user. The code is written in Ruby and is designed to be used within the Metasploit framework. The only relevant endpoint is the HTTPS interface on port 7443, specifically the /admin/test_li_connection.php path.
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.