Dahua devices with Build time before December 2019 use strong security login mode by default, but in order to be compatible with the normal
Dahua devices with Build time before December 2019 use strong security login mode by default, but in order to be compatible with the normal login of early devices, some devices retain the weak security login mode that users can control. If the user uses a weak security login method, an attacker can monitor the device network to intercept network packets to attack the device. So it is recommended that the user disable this login method.
- Published
- May 13, 2020
- Updated
- Jun 16, 2026
- EPSS
- 0.9% · 57th percentile
- CWE
- CWE-276
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.9%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| dahuasecurity | sd6al firmware | cpe:2.3:o:dahuasecurity:sd6al_firmware |
| dahuasecurity | sd6al | cpe:2.3:h:dahuasecurity:sd6al |
| dahuasecurity | sd5a firmware | cpe:2.3:o:dahuasecurity:sd5a_firmware |
| dahuasecurity | sd5a | cpe:2.3:h:dahuasecurity:sd5a |
| dahuasecurity | sd1a firmware | cpe:2.3:o:dahuasecurity:sd1a_firmware |
| dahuasecurity | sd1a | cpe:2.3:h:dahuasecurity:sd1a |
| dahuasecurity | ptz1a firmware | cpe:2.3:o:dahuasecurity:ptz1a_firmware |
| dahuasecurity | ptz1a | cpe:2.3:h:dahuasecurity:ptz1a |
| dahuasecurity | sd50 firmware | cpe:2.3:o:dahuasecurity:sd50_firmware |
| dahuasecurity | sd50 | cpe:2.3:h:dahuasecurity:sd50 |
| dahuasecurity | sd52c firmware | cpe:2.3:o:dahuasecurity:sd52c_firmware |
| dahuasecurity | sd52c | cpe:2.3:h:dahuasecurity:sd52c |
and 28 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- dahuasecurity ipc-hdbw1320e-w firmwarebefore 2019-12
- dahuasecurity ipc-hx2xxx firmwarebefore 2019-12
- dahuasecurity ipc-hx5842h firmwarebefore 2019-12
- dahuasecurity ipc-hx7842h firmwarebefore 2019-12
- dahuasecurity ipc-hxxx5x4x firmwarebefore 2019-12
- dahuasecurity n42b1p firmwarebefore 2019-12
- dahuasecurity n42b2p firmwarebefore 2019-12
- dahuasecurity n42b3p firmwarebefore 2019-12
- dahuasecurity n52a4p firmwarebefore 2019-12
- dahuasecurity n52b2p firmwarebefore 2019-12
- dahuasecurity n52b3p firmwarebefore 2019-12
- dahuasecurity n52b5p firmwarebefore 2019-12
- dahuasecurity n54a4p firmwarebefore 2019-12
- dahuasecurity n54b2p firmwarebefore 2019-12
- dahuasecurity ptz1a firmwarebefore 2019-12
- dahuasecurity sd1a firmwarebefore 2019-12
- dahuasecurity sd50 firmwarebefore 2019-12
- dahuasecurity sd52c firmwarebefore 2019-12
- dahuasecurity sd5a firmwarebefore 2019-12
- dahuasecurity sd6al firmwarebefore 2019-12
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.
n/a IPC-HX2XXX Series,IPC-HXXX5X4X Series,IPC-HX5842H,IPC-HX7842H,NVR 5x Series,NVR 4x Series,SD6AL Series,SD5A Series,SD1A Series,PTZ1A Series,SD50/52C Series,IPC-HDBW1320E-W
- Versions which Build time before December,2019affected
Same product
dahuasecurity: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-9502Some Dahua products with Build time before December 2019 have Session ID predictable vulnerabilities.39Monitor
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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-276 · Incorrect Default PermissionsCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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.
Attack patterns (CAPEC)
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
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.