dbcve.org
Nvr4104 4ks2\/l FirmwareOperating system · Dahuasecurity

CVE-2024-39949

HIGH · 7.5 CVSS v3.1 Published 2024-07-31
Fix available
A fix is available. Upgrade to 4.003.0000000.1.r.240515 or later.
See remediation →
84/100
Remediation priority · High
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 vulnerability has been found in Dahua products. Attackers can send carefully crafted data packets to the interface with vulnerabilities, causing the device to crash.

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 · moderate confidence

A denial-of-service vulnerability in Dahua surveillance products allows remote attackers to crash affected devices by sending specially crafted network packets to a vulnerable interface. The vulnerability is network-exploitable and requires no authentication.

MitigationApply network segmentation to isolate Dahua devices, implement IPS/IDS rules to detect and block anomalous packet patterns, and monitor for official firmware updates from Dahua.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Nvr4104 4ks2\/l FirmwareOperating system
Affected:< 4.003.0000000.1.r.240515
Nvr4108 4ks2\/l FirmwareOperating system
Affected:= 4.003.0000000.1.r.240515
Nvr4116 4ks2\/l FirmwareOperating system
Affected:< 4.003.0000000.1.r.240515
Nvr4104 P 4ks2\/l FirmwareOperating system
Affected:< 4.003.0000000.1.r.240515
Nvr4108 P 4ks2\/l FirmwareOperating system
Affected:< 4.003.0000000.1.r.240515
Nvr4108 8p 4ks2\/l FirmwareOperating system
Affected:< 4.003.0000000.1.r.240515
Nvr4116 8p 4ks2\/l FirmwareOperating system
Affected:< 4.003.0000000.1.r.240515
Nvr4104hs 4ks2\/l FirmwareOperating system
Affected:< 4.003.0000000.1.r.240515

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
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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 Dahua NVR models on the network
    Use network scanning tools (e.g., nmap, Angry IP Scanner) or check device inventory to identify any Dahua NVR devices. Look for products: NVR4104, NVR4108, NVR4116, NVR4104P, NVR4108P, NVR4108-8P, NVR4116-8P, or NVR4104HS.
    Affected if Any of these specific Dahua NVR models are present on the network.
  2. Locate the web interface or management portal
    Access the device web interface via its IP address on the network (typically ports 80 or 443). The Dahua web interface is usually accessible at http://[device-ip]/ or https://[device-ip]/.
    Affected if The device web interface is accessible over the network.
  3. Check the firmware version
    Log into the Dahua NVR web interface and navigate to Setup > System > About or similar path to view the firmware version. Alternatively, use the ONVIF protocol or manufacturer tools to query device information.
    Affected if The firmware version is either < 4.003.0000000.1.r.240515 OR equals exactly 4.003.0000000.1.r.240515 (for NVR4108 4ks2/l model only).
  4. Verify network exposure
    Check if the device management ports (HTTP/HTTPS, RTSP, or proprietary Dahua ports) are exposed to untrusted networks such as the public internet or less-trusted network segments.
    Affected if The device is directly reachable from untrusted networks without firewall segmentation.

You are affected if you have any of the listed Dahua NVR models running firmware version lower than or equal to 4.003.0000000.1.r.240515, and the device is network-accessible to potential attackers.

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
Upgrade available Upgrade to 4.003.0000000.1.r.240515 or later
Fixed in 4.003.0000000.1.r.240515
Interim mitigation

Apply network segmentation to isolate Dahua devices, implement IPS/IDS rules to detect and block anomalous packet patterns, and monitor for official firmware updates from Dahua.

Recommended fix High confidence

4.003.0000000.1.r.240515 or later

  1. Identify the specific NVR model from the affected product list (Nvr4104, Nvr4108, Nvr4116, Nvr4104 P, Nvr4108 P, Nvr4108 8p, Nvr4116 8p, or Nvr4104hs)
  2. Access the device administrative interface via web browser or management software
  3. Navigate to the firmware update or system maintenance section
  4. Download the firmware version 4.003.0000000.1.r.240515 or later from the official Dahua Security website (www.dahuasecurity.com)
  5. Upload the firmware file to the device and initiate the upgrade process
  6. Allow the device to complete the reboot cycle without interruption
  7. Verify the firmware version has been successfully updated after the device restarts
Caveat Firmware upgrades may temporarily disrupt recording and network connectivity; ensure backup power and schedule during maintenance window

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

Fix this in Nvr4104 4ks2\/l Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-39949 — 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-39949 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