CVE-2024-39947
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 has been found in Dahua products.After obtaining the ordinary user's username and password, the attacker can send a carefully crafted data packet 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 confidenceAuthenticated denial-of-service vulnerability in Dahua products where an attacker with valid user credentials can send a specially crafted data packet to a vulnerable interface, causing the device to crash. The attack requires prior authentication, indicating the vulnerability lies in improper input validation within an authenticated API endpoint.
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< 4.003.0000000.1.r.240515= 4.003.0000000.1.r.240515< 4.003.0000000.1.r.240515< 4.003.0000000.1.r.240515< 4.003.0000000.1.r.240515< 4.003.0000000.1.r.240515< 4.003.0000000.1.r.240515< 4.003.0000000.1.r.240515CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the NVR device modelAccess the device web interface or use the ONVIF/Dahua SDK to query the device model information. Look for model numbers: Nvr4104, Nvr4108, Nvr4116, Nvr4104P, Nvr4108P, Nvr4108-8p, Nvr4116-8p, or Nvr4104hs.Affected if The device model matches any of the following: Nvr4104 4ks2/l, Nvr4108 4ks2/l, Nvr4116 4ks2/l, Nvr4104 P 4ks2/l, Nvr4108 P 4ks2/l, Nvr4108 8p 4ks2/l, Nvr4116 8p 4ks2/l, or Nvr4104hs 4ks2/l.
-
Check the installed firmware versionLog into the device web interface and navigate to the System or About section to view the firmware version. Alternatively, use the Dahua API or SNMP to query the firmware version programmatically.Affected if The firmware version is lower than 4.003.0000000.1.r.240515, or exactly equals 4.003.0000000.1.r.240515 for the Nvr4108 4ks2/l model.
-
Verify remote API access is enabledCheck the device network settings to confirm if the web server or API services are enabled. Look for HTTP/HTTPS ports (typically 80/443) or the Dahua API port (typically 8000) that are open and accessible.Affected if The device has its web interface or API services enabled and accessible over the network, as this is the attack vector for the authenticated API endpoint.
-
Confirm authentication is requiredNote that this vulnerability requires valid user credentials to exploit. Review the device user accounts and confirm that user authentication is enforced for API access.Affected if User authentication is configured and enabled on the device, which is required for the exploit to function.
The device is affected if it is one of the listed NVR models (Nvr4104/08/16 variants or Nvr4104hs) running firmware version 4.003.0000000.1.r.240515 or lower, and the remote API/web interface is accessible with valid credentials.
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.
dbcve · scoped4.003.0000000.1.r.240515
Apply vendor-provided firmware updates from Dahua. Until patched, limit credential exposure and implement network segmentation to reduce attack surface. Monitor for unusual authentication patterns.
Firmware version 4.003.0000000.1.r.240515 or later (check Dahua.com for the latest available build)
- 1. Identify the exact model number of your Dahua NVR device from the affected list (Nvr4104, Nvr4108, Nvr4116, Nvr4104P, Nvr4108P, Nvr4108 8p, Nvr4116 8p, or Nvr4104hs)
- 2. Access the device's web interface or use the Dahua ConfigTool to check the current firmware version
- 3. Navigate to the official Dahua Security website (www.dahuasecurity.com) and locate the download/support section for your specific NVR model
- 4. Download the latest firmware version. Based on the advisory, ensure the version is 4.003.0000000.1.r.240515 or later
- 5. Before upgrading, backup the device configuration if possible
- 6. Upload and apply the firmware update through the NVR's web interface or via Dahua's upgrade tool
- 7. After the upgrade completes, verify the device is functioning normally and confirm the new firmware version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39947 — 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-39947 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