CVE-2023-33617 is an OS command injection vulnerability in Parks Fiberlink 210 firmware version V2.1.14_X000. The issue is present in the /boaform/admin/formPing endpoint, where the target_addr parameter is insufficiently sanitized before being used by server-side functionality associated with ping operations. An attacker can supply crafted input to target_addr to inject and execute arbitrary operating system commands on the affected device.
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 provides an operational exploit for CVE-2023-33617, an authenticated OS command injection vulnerability in Parks FiberLink 210 routers running firmware version V2.1.14_X000. The main script, 'exploit.py', is a Python tool that automates the process of discovering vulnerable routers using the Shodan and ZoomEye APIs, authenticating with default or user-supplied credentials, and exploiting the command injection via the '/boaform/admin/formPing' endpoint. The tool supports multi-threaded exploitation and outputs a list of vulnerable hosts and their command output. The repository includes a README with detailed usage instructions and a requirements.txt for dependencies. The exploit is operational, as it provides a working payload and automates the full attack chain from discovery to exploitation. Key fingerprintable endpoints include the router's login, status, and ping form URLs.
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.