TVT DVR TD-2104TS-CL: attackers can read data they should not see
OFFICIAL NAME: TVT DVR TD-2104TS-CL queryDevInfo information disclosure
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 has been found in TVT DVR TD-2104TS-CL, DVR TD-2108TS-HP, Provision-ISR DVR SH-4050A5-5L(MM) and AVISION DVR AV108T and classified as problematic. This vulnerability affects unknown code of the file /queryDevInfo. The manipulation leads to information disclosure. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.
WHY THIS VERDICT Attack attempts are confirmed, with no confirmed exploitation yet.
WHY IT RANKS HERE Ready-made attack tools are public. The first report is 19 days old. 4 products are affected.
- HIGHEST CONFIRMED RUNG
- TRIED
- CISA KEV
- NOT YET
- EXPLOIT CODE
- READY TO USE
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-7339 seen by honeypots (Shadowserver via CIRCL).
04 EXPLOITED
□ NO EVIDENCE YETNEWEST EVIDENCE NONE YETNo evidence yet.
SRC: NONE YET05 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 TVT DVR TD-2104TS-CL? 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
- JUL 31, 2024CISA Vulnrichment notes a public proof of concept for CVE-2024-7339
- AUG 5, 20241 public GitHub repository claims a proof of concept for CVE-2024-7339
- Attack activity. OCT 22, 2026Attack attempts on CVE-2024-7339 seen by honeypots (Shadowserver via CIRCL)
SOURCES
- [1] nuclei-templates: Nuclei scan template: TVT DVR Sensitive Device - Information Disclosure, OCT 24
- [2] CIRCL Vulnerability-Lookup sightings: Attack attempts on CVE-2024-7339 seen by honeypots (Shadowserver via CIRCL), OCT 22
- [3] PoC-in-GitHub: 1 public GitHub repository claims a proof of concept for CVE-2024-7339, AUG 5
- [4] CVE List V5 and CISA Vulnrichment: CISA Vulnrichment notes a public proof of concept for CVE-2024-7339, JUL 31