CVE-2024-3721

CRITICALNVD 6.39.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 86% probability of exploitation within the next 30 days (top 0.3% of all CVEs). NVD baseline CVSS 6.3 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Trending — 3 sources updated this weekWeaponized
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 86%
  • Public exploit code is available (ssvc poc, epss top5pct, epss high)
CISA-KEV: Not listedEPSS PROB: 86%CVSS: 6.3Exploit: ssvc poc · epss top5pct · epss highExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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. The identifier VDB-260573 was assigned to this vulnerability.

CVSS v3
6.3
EG Score
9.0(high)
EG Risk
75(Track)
EG Risk 75/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation86% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
86%
EPSS %ILE
100%
KEV
Not listed

Published

April 13, 2024

Last Modified

April 15, 2026

References (8)

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 12× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:16 UTCEPSS rescore
  2. 2026-07-23 02:38 UTCEG score recompute
  3. 2026-07-22 21:22 UTCEG score recompute▲ 2.70
  4. 2026-07-22 21:21 UTCGHSA enrichment
  5. 2026-07-22 14:07 UTCEPSS rescore
  6. 2026-07-20 17:06 UTCEPSS rescore
  7. 2026-07-15 16:56 UTCEPSS rescore
  8. 2026-07-15 16:56 UTCEPSS rescore
  9. 2026-07-13 22:29 UTCEPSS rescore
  10. 2026-07-13 06:12 UTCEPSS rescore
  11. 2026-07-11 08:26 UTCEPSS rescore
  12. 2026-07-01 15:05 UTCEPSS rescore
  13. 2026-06-27 03:07 UTCEPSS rescore
  14. 2026-06-27 03:07 UTCEPSS rescore
  15. 2026-06-24 14:04 UTCEPSS rescore
  16. 2026-06-24 14:04 UTCEPSS rescore
  17. 2026-06-23 21:32 UTCEPSS rescore
  18. 2026-06-23 21:32 UTCEPSS rescore
  19. 2026-06-18 17:52 UTCEPSS rescore
  20. 2026-06-18 17:52 UTCEPSS rescore
  21. 2026-06-17 17:52 UTCEPSS rescore
  22. 2026-06-15 17:47 UTCEPSS rescore
  23. 2026-06-14 23:17 UTCEPSS rescore
  24. 2026-06-12 23:11 UTCEPSS rescore
  25. 2026-06-12 23:11 UTCEPSS rescore
Show 36 more
  1. 2026-06-11 13:59 UTCEPSS rescore
  2. 2026-06-10 22:18 UTCEPSS rescore
  3. 2026-06-10 13:21 UTCEPSS rescore
  4. 2026-06-07 15:24 UTCEPSS rescore
  5. 2026-06-07 15:24 UTCEPSS rescore
  6. 2026-06-06 13:46 UTCEPSS rescore
  7. 2026-06-06 13:46 UTCEPSS rescore
  8. 2026-06-05 22:46 UTCEPSS rescore
  9. 2026-06-05 22:46 UTCEPSS rescore
  10. 2026-06-05 06:09 UTCEPSS rescore
  11. 2026-06-05 06:09 UTCEPSS rescore
  12. 2026-06-02 20:12 UTCEPSS rescore
  13. 2026-06-01 13:51 UTCEPSS rescore
  14. 2026-06-01 13:51 UTCEPSS rescore
  15. 2026-05-31 00:15 UTCEPSS rescore
  16. 2026-05-31 00:15 UTCEPSS rescore
  17. 2026-05-29 13:43 UTCEPSS rescore
  18. 2026-05-28 13:44 UTCEPSS rescore
  19. 2026-05-28 13:44 UTCEPSS rescore
  20. 2026-05-28 13:44 UTCEPSS rescore
  21. 2026-05-27 13:40 UTCEPSS rescore
  22. 2026-05-27 13:40 UTCEPSS rescore
  23. 2026-05-27 13:40 UTCEPSS rescore
  24. 2026-05-26 07:18 UTCEPSS rescore
  25. 2026-05-26 07:18 UTCEPSS rescore
  26. 2026-05-26 07:18 UTCEPSS rescore
  27. 2026-05-22 21:16 UTCEPSS rescore
  28. 2026-05-22 21:16 UTCEPSS rescore
  29. 2026-05-22 21:16 UTCEPSS rescore
  30. 2026-05-22 21:16 UTCEPSS rescore
  31. 2026-05-22 03:12 UTCEG score recompute
  32. 2026-05-22 03:12 UTCGHSA enrichment
  33. 2026-05-18 21:30 UTCEPSS rescore
  34. 2026-05-18 21:30 UTCEPSS rescore
  35. 2026-05-18 21:30 UTCEPSS rescore
  36. 2026-05-18 21:30 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-3721?
CVE-2024-3721 is a critical vulnerability published on April 13, 2024. 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=SOSTREAMAX_. The manipulation of the argument mdb/mdc leads to os command injection. The attack may be initiated remotely.…
When was CVE-2024-3721 disclosed?
CVE-2024-3721 was first published in the National Vulnerability Database on April 13, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-3721 actively exploited?
CVE-2024-3721 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 86% probability of exploitation in the next 30 days, which ranks it in the top 0.3% of all scored CVEs.
What is the CVSS score of CVE-2024-3721?
CVE-2024-3721 has a CVSS v3 base score of 6.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2024-3721?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-3721, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-3721

Explore →

Is Your Infrastructure Affected by CVE-2024-3721?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs