TBK DVR-4104: attackers can run commands on it
OFFICIAL NAME: TBK DVR-4104/DVR-4216 os command injection
WHAT IT IS · ROUTERS, CAMERAS AND DEVICESRouters, cameras and recorders are often forgotten and rarely updated.
DO THIS FIRSTUpdate it or replace it. Never leave its admin page open to the internet. Not sure if you use it? Send this page to your IT provider or security lead and ask.
TECHNICAL SUMMARY A vulnerability was found in TBK DVR-4104 and DVR-4216 up to 20240412 and classified as critical. This issue affects some unknown processing of the file /device.rsp?opt=sys&cmd=___S_O_S_T_R_E_A_MAX___. The manipulation of the argument mdb/mdc leads to os command injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.
WHY THIS VERDICT Attacks are reported but not confirmed by an authoritative source, and the vulnerability is more than 90 days old.
WHY IT RANKS HERE Exploitation is reported. The first report is 19 days old.
- HIGHEST CONFIRMED RUNG
- TRIED
- CISA KEV
- NOT YET
- EXPLOIT CODE
- PROOF OF CONCEPT
How far has it climbed?
01 TALK
□ NO EVIDENCE YETNEWEST EVIDENCE NONE YETNo evidence yet.
SRC: NONE YET02 EXPOSED
□ NOT TRACKED YETNO SOURCE FOR THIS STEP YETWe have no source that counts exposed systems yet. Internet scan data needs a partnership we do not have. No evidence here does not mean nothing is exposed.
03 TRIED
■ CONFIRMEDNEWEST EVIDENCE · 1 SOURCEAttack attempts on CVE-2024-3721 seen by honeypots (Shadowserver via CIRCL).
04 EXPLOITED
▨ REPORTED, NOT CONFIRMEDNEWEST EVIDENCE · 1 SOURCEExploitation of CVE-2024-3721 reported (CIRCL sighting).
05 DAMAGE
□ NOT TRACKED YETNO SOURCE FOR THIS STEP YETBreach notices and filings rarely name the flaw that was used, so we cannot link them to this event yet. No evidence here does not mean no harm.
When each thing happened
- DISCLOSED
- EXPLOIT CODE PUBLICDATE UNKNOWN
- FIRST ATTACK REPORT
- CISA KEV LISTINGNOT YET
- US FEDERAL DEADLINENOT YET
Questions to ask this week
- Do we run TBK DVR-4104? If yes, is it patched or cut off from the internet?
- Who owns fixing it, and by what date?
- Have we checked for signs of attack since the first report, not just since the patch?
How it unfolded
- APR 13, 2024CISA Vulnrichment notes a public proof of concept for CVE-2024-3721
- Attack activity. OCT 22, 2026Attack attempts on CVE-2024-3721 seen by honeypots (Shadowserver via CIRCL)
- Attack activity. NOV 7, 2026Exploitation of CVE-2024-3721 reported (CIRCL sighting)
SOURCES
- [1] CIRCL Vulnerability-Lookup sightings: Exploitation of CVE-2024-3721 reported (CIRCL sighting), NOV 7
- [2] CIRCL Vulnerability-Lookup sightings: Attack attempts on CVE-2024-3721 seen by honeypots (Shadowserver via CIRCL), OCT 22
- [3] CVE List V5 and CISA Vulnrichment: CISA Vulnrichment notes a public proof of concept for CVE-2024-3721, APR 13