The UpdateCertificatesServlet in the SNAC registration server component of HP ProCurve Manager (PCM) 3.20 and 4.0, PCM+ 3.20 and 4.0, and Identity Driven Manager (IDM) 4.0 fails to properly validate the fileName argument. This allows remote attackers to upload arbitrary files, including .jsp web shells, to the server. As a result, attackers can execute arbitrary code on the affected system by accessing the uploaded .jsp files.
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 targeting HP ProCurve Manager 4.0 SNAC Server (CVE-2013-4812). The exploit leverages a path traversal vulnerability in the UpdateCertificatesServlet, allowing unauthenticated attackers to upload arbitrary JSP files (webshells or command payloads) to the server. The module first obtains a session cookie, then uploads a malicious JSP file using a crafted multipart POST request to /RegWeb/RegWeb/UpdateCertificatesServlet, and finally executes the payload by requesting the uploaded JSP. The exploit provides remote code execution capabilities on the target Windows server. The code is written in Ruby and follows standard Metasploit module structure, with clear separation of session handling, vulnerability checking, file upload, and payload execution. The main network endpoints involved are the servlet upload and status check URLs under the /RegWeb/ 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.