CVE-2024-39945: A vulnerability has been found in Dahua products.
Noroxi assessment
Priority: Monitor (action score 19/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.45% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A vulnerability has been found in Dahua products. After obtaining the administrator's username and password, the attacker can send a carefully crafted data packet to the interface with vulnerabilities, causing the device to crash.
- Published
- Jul 31, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.4% · 40th percentile
- CWE
- CWE-703
Report tools
Action score
19
Low priority for now.
- CVSS
- 19 / 40 · 4.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 4.9
- CNA · dahua
- 4.9
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| dahuasecurity | nvr4104-4ks2\/l firmware | cpe:2.3:o:dahuasecurity:nvr4104-4ks2\/l_firmware |
| dahuasecurity | nvr4104-4ks2\/l | cpe:2.3:h:dahuasecurity:nvr4104-4ks2\/l |
| dahuasecurity | nvr4108-4ks2\/l firmware | cpe:2.3:o:dahuasecurity:nvr4108-4ks2\/l_firmware |
| dahuasecurity | nvr4108-4ks2\/l | cpe:2.3:h:dahuasecurity:nvr4108-4ks2\/l |
| dahuasecurity | nvr4116-4ks2\/l firmware | cpe:2.3:o:dahuasecurity:nvr4116-4ks2\/l_firmware |
| dahuasecurity | nvr4116-4ks2\/l | cpe:2.3:h:dahuasecurity:nvr4116-4ks2\/l |
| dahuasecurity | nvr4104-p-4ks2\/l firmware | cpe:2.3:o:dahuasecurity:nvr4104-p-4ks2\/l_firmware |
| dahuasecurity | nvr4104-p-4ks2\/l | cpe:2.3:h:dahuasecurity:nvr4104-p-4ks2\/l |
| dahuasecurity | nvr4108-p-4ks2\/l firmware | cpe:2.3:o:dahuasecurity:nvr4108-p-4ks2\/l_firmware |
| dahuasecurity | nvr4108-p-4ks2\/l | cpe:2.3:h:dahuasecurity:nvr4108-p-4ks2\/l |
| dahuasecurity | nvr4108-8p-4ks2\/l firmware | cpe:2.3:o:dahuasecurity:nvr4108-8p-4ks2\/l_firmware |
| dahuasecurity | nvr4108-8p-4ks2\/l | cpe:2.3:h:dahuasecurity:nvr4108-8p-4ks2\/l |
and 100 more
Versions reported by the vendor
Affected version ranges reported by the assigning authority (dahua). Independent of NVD's CPE analysis and usually ahead of it.
Dahua NVR4XXX
- NVR4XXX Versions which Build time before 2023/12/13affected
Affected versions · NVD (20)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- dahuasecurity nvr4104-4ks2/l firmwarebefore 4.003.0000000.1.r.240515
- dahuasecurity nvr4104-4ks3 firmwarebefore 4.003.0000000.0.r.240312
- dahuasecurity nvr4104-p-4ks2/l firmwarebefore 4.003.0000000.1.r.240515
- dahuasecurity nvr4104-p-4ks3 firmwarebefore 4.003.0000000.0.r.240312
- dahuasecurity nvr4104-p-4ks3(960g) firmwarebefore 4.003.0000000.0.r.240312
- dahuasecurity nvr4104hs-4ks2/l firmwarebefore 4.003.0000000.1.r.240515
- dahuasecurity nvr4104hs-4ks3 firmwarebefore 4.003.0000000.0.r.240312
- dahuasecurity nvr4104hs-4ks3(960g) firmwarebefore 4.003.0000000.0.r.240312
- dahuasecurity nvr4104hs-p-4ks2/l firmwarebefore 4.003.0000000.1.r.240515
- dahuasecurity nvr4104hs-p-4ks3 firmwarebefore 4.003.0000000.0.r.240312
- dahuasecurity nvr4104hs-p-4ks3(960g) firmwarebefore 4.003.0000000.0.r.240312
- dahuasecurity nvr4108-4ks2/l firmware4.003.0000000.1.r.240515
- dahuasecurity nvr4108-4ks3 firmwarebefore 4.003.0000000.0.r.240312
- dahuasecurity nvr4108-8p-4ks2/l firmwarebefore 4.003.0000000.1.r.240515
- dahuasecurity nvr4108-8p-4ks3 firmwarebefore 4.003.0000000.0.r.240312
- dahuasecurity nvr4108-p-4ks2/l firmwarebefore 4.003.0000000.1.r.240515
- dahuasecurity nvr4108-p-4ks3 firmwarebefore 4.003.0000000.0.r.240312
- dahuasecurity nvr4108hs-4ks2/l firmwarebefore 4.003.0000000.1.r.240515
- dahuasecurity nvr4108hs-4ks3 firmwarebefore 4.003.0000000.0.r.240312
- dahuasecurity nvr4108hs-4ks3(960g) firmwarebefore 4.003.0000000.0.r.240312
Same product
dahuasecurity: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-39950A vulnerability has been found in Dahua products.39Monitor
- CVE-2024-39949A vulnerability has been found in Dahua products.30Monitor
- CVE-2024-39948A vulnerability has been found in Dahua products.30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-39944Jul 31, 2024 · A vulnerability has been found in Dahua products.Attackers
can send carefully crafted data packets to the interface with…30Monitor
- Later →CVE-2024-39946Jul 31, 2024 · A vulnerability has been found in Dahua products.After obtaining the administrator's username and password, the attacker can send a…28Monitor
- Later →CVE-2024-39947Jul 31, 2024 · A vulnerability has been found in Dahua products.After obtaining the ordinary user's username and password, the attacker can send a…26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-703 · Improper Check or Handling of Exceptional ConditionsCVSS vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.