CVE-2024-3721
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOS command injection vulnerability in TBK DVR-4104 and DVR-4216 digital video recorders. The /device.rsp endpoint fails to sanitize the mdb/mdc parameter before passing it to system commands, allowing remote attackers to execute arbitrary OS commands via crafted requests to the sys command handler.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the DVR web interface or check physical device labeling for model number TBK DVR-4104 or DVR-4216Affected if Device is a TBK DVR-4104 or DVR-4216 model
-
Check firmware versionLog into the DVR admin interface and navigate to System > Information, or send an HTTP request to the device to retrieve the firmware version stringAffected if Firmware version is unknown, unpatched, or falls within any known affected version range provided by TBK
-
Verify web interface accessibilityAttempt to access http://[DVR-IP]/device.rsp from a browser or curl command to confirm the /device.rsp endpoint is reachableAffected if The /device.rsp endpoint responds and is accessible over the network
-
Confirm vulnerable parameter existsSend a benign test request to /device.rsp with the sys command handler and observe if the mdb or mdc parameters are accepted (note: do not inject actual commands)Affected if The endpoint accepts sys command handler requests with mdb/mdc parameters without requiring authentication or validation errors
-
Check network exposureReview firewall rules, NAT configurations, or VLAN settings to determine if the DVR management web interface is accessible from untrusted networks or the internetAffected if The DVR web interface is directly exposed to the internet or untrusted internal networks
The environment is affected if it contains a TBK DVR-4104 or DVR-4216 with an unpatched firmware version and the /device.rsp endpoint with sys command handler is accessible over the network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict network exposure of the DVR management interface via firewall or VLAN isolation immediately, as a public exploit exists. Contact TBK for firmware updates; if unavailable, evaluate replacement with a currently supported device.
- Consultation3.0 h
- Implementation10.0 h
- Testing5.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3721 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-3721 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data