Hero Qubo HCD01_02_V1.38_20220125 devices are configured to allow TELNET access with root privileges by default, and do not require a password for authentication. This exposes the device to unauthenticated remote access with full administrative rights.
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 a working exploit for CVE-2023-22906, a critical vulnerability in the Hero Qubo Smart Doorbell (HCD01_02_V1.38_20220125). The main exploit script, Qubo_Scanner.py, scans the local network for devices with open Telnet (port 23), attempts to connect, and provides unauthenticated root shell access if successful. The exploit leverages the fact that the device's Telnet service is enabled by default with no password for the root account. The repository also contains extracted audio files and a firmware analysis report, but the core exploit is the Python script. The attack vector is network-based, requiring local network access. The exploit is operational, providing a real shell payload, and targets a specific IoT device and firmware version. The exploit can be used to fully compromise the device, extract data, or use it as part of a botnet. No fake or destructive code is present; the exploit is legitimate and functional.
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.