CVE-2012-6610 is a command injection vulnerability affecting Polycom HDX Video End Points before 3.0.4 and UC APL before 2.7.1.J. The issue is present in the ping command feature, which insufficiently sanitizes user-supplied input before passing it to an underlying system command. As described, a remote authenticated user can inject shell metacharacters, specifically a semicolon (;), to append and execute arbitrary commands on the target system.
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 exploit module targeting Polycom HDX video endpoints (versions 3.0.5 and earlier) vulnerable to an authentication bypass in the command shell (telnet) service. The exploit works by making multiple simultaneous connections to the telnet service (default port 23), exploiting a race condition to bypass authentication and gain access to a restricted shell. For versions prior to 3.0.4, the exploit leverages a command injection vulnerability in the 'ping' command to execute arbitrary commands as root, typically resulting in a reverse shell to the attacker's system. The module is written in Ruby and follows standard Metasploit conventions, with configurable options for target host, port, and callback parameters. The main attack vector is network-based, targeting the telnet service. The only code file present is the exploit module itself.
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.