Loading vulnerability…
ContentKeeper Web Appliance versions prior to 125.10 expose the mimencode binary through a CGI endpoint at /cgi-bin/ck/mimencode. The endpoint can be abused by an unauthenticated remote attacker via a crafted POST request containing traversal and output parameters, causing the appliance to return arbitrary files from the underlying filesystem rather than restricting access to intended webroot content. The issue is effectively a path traversal/arbitrary file read condition that allows access to sensitive local files such as /etc/passwd.
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 auxiliary module targeting ContentKeeper Web Appliances vulnerable to CVE-2009-10005. The exploit abuses the 'mimencode' CGI binary to perform arbitrary file reads outside the webroot via a crafted POST request that leverages path traversal. The module first sends a POST request to the mimencode endpoint, instructing it to encode and write the contents of a specified file (default: /etc/passwd) to a temporary, web-accessible file. It then retrieves this file via a GET request, decodes the base64 content, and displays the result. The module is operational and can be used to extract sensitive files from vulnerable appliances. The only file in the repository is a Ruby script designed for use within the Metasploit framework, and it requires network access to the target's HTTP interface. The main fingerprintable endpoints are the mimencode CGI path and the files accessed or created during exploitation.
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.
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.