dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2024-13985

CRITICAL · 10.0 CVSS v4.0 Published 2025-08-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A command injection vulnerability in Dahua EIMS versions prior to 2240008 allows unauthenticated remote attackers to execute arbitrary system commands via the capture_handle.action interface. The flaw stems from improper input validation in the captureCommand parameter, which is processed without sanitization or authentication. By sending crafted HTTP requests, attackers can inject OS-level commands that are executed on the server, leading to full system compromise. Exploitation evidence was first observed by the Shadowserver Foundation on 2024-04-06 UTC.

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 confidence

A command injection vulnerability in Dahua EIMS allows unauthenticated remote attackers to execute arbitrary system commands through the capture_handle.action interface. The captureCommand parameter is processed without sanitization or authentication, enabling OS-level command injection. This leads to full system compromise as attackers can execute any command on the server.

MitigationUpgrade Dahua EIMS to version 2240008 or later. If immediate patching is not possible, restrict network access to the affected interface using firewall rules or network segmentation, and implement WAF signatures to detect and block command injection attempts.

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Dahua EIMS is installed
    Look for Dahua EIMS processes or services running on the system, or check for EIMS installation directories in common locations
    Affected if Dahua EIMS software is found running on the system
  2. Determine the installed version of Dahua EIMS
    Locate the version information for the EIMS installation (check about pages, version files, or management console) and compare it to version 2240008
    Affected if The installed version is lower than 2240008
  3. Verify if the web management interface is accessible
    Check if the EIMS web interface port (typically 80/443) is listening and accessible on network interfaces
    Affected if The web management interface is exposed and responds to requests
  4. Confirm the capture_handle.action endpoint exists
    Probe the capture_handle.action endpoint on the EIMS web server to verify it is present and responding
    Affected if The capture_handle.action endpoint is accessible and responds to requests

The system is affected if Dahua EIMS is running with a version lower than 2240008 and the capture_handle.action web interface is network-accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Dahua EIMS to version 2240008 or later. If immediate patching is not possible, restrict network access to the affected interface using firewall rules or network segmentation, and implement WAF signatures to detect and block command injection attempts.

Recommended fix High confidence

Dahua EIMS version 2240008

  1. Identify the current Dahua EIMS version by accessing the system administration interface or checking system information
  2. Upgrade Dahua EIMS to version 2240008 or later from the official Dahua support portal (support.dahuatech.com)
  3. After upgrading, verify the capture_handle.action interface no longer accepts unsanitized input in the captureCommand parameter
  4. Review system logs for any signs of compromise or unauthorized access that may have occurred prior to patching
  5. If compromise is suspected, conduct a full forensic investigation and rebuild affected systems from known-good backups

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13985 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-13985 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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