CVE-2020-28188 is a remote command execution vulnerability in TerraMaster TOS affecting versions up to and including 4.2.06. The flaw is caused by insufficient input validation of the event parameter in the makecvs.php endpoint. A remote, unauthenticated attacker can supply crafted input to inject operating system commands, which are then executed by the underlying system. Because exploitation occurs through a network-accessible web component and does not require prior authentication, the vulnerability can be used to fully compromise exposed TerraMaster NAS devices running vulnerable TOS releases.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability affecting TerraMaster TOS 4.2.06 and earlier that Necro is still exploiting.
Unknown (content lists this CVE in activity tables without describing the vulnerability).
Vulnerability observed in exploitation telemetry (details not specified in the content).
A remote code execution vulnerability in TerraMaster TOS that the MANGA Mirai variant attempts to exploit.
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.