Dahua DVR appliances have a hardcoded password for (1) the root account and (2) an unspecified "backdoor" account, which makes it easier for
Dahua DVR appliances have a hardcoded password for (1) the root account and (2) an unspecified "backdoor" account, which makes it easier for remote attackers to obtain administrative access via authorization requests involving (a) ActiveX, (b) a standalone client, or (c) unknown other vectors.
- Published
- Sep 17, 2013
- Updated
- Jun 16, 2026
- EPSS
- 10.3% · 96th percentile
- CWE
- CWE-255
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
43
Plan
Add it to your regular patch cycle.
- CVSS
- 40 / 40 · 10.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 3 / 30 · 10.3%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| dahuasecurity | dvr0404hd-a | cpe:2.3:h:dahuasecurity:dvr0404hd-a |
| dahuasecurity | dvr0404hd-l | cpe:2.3:h:dahuasecurity:dvr0404hd-l |
| dahuasecurity | dvr0404hd-s | cpe:2.3:h:dahuasecurity:dvr0404hd-s |
| dahuasecurity | dvr0404hd-u | cpe:2.3:h:dahuasecurity:dvr0404hd-u |
| dahuasecurity | dvr0404hf-a-e | cpe:2.3:h:dahuasecurity:dvr0404hf-a-e |
| dahuasecurity | dvr0404hf-al-e | cpe:2.3:h:dahuasecurity:dvr0404hf-al-e |
| dahuasecurity | dvr0404hf-s-e | cpe:2.3:h:dahuasecurity:dvr0404hf-s-e |
| dahuasecurity | dvr0404hf-u-e | cpe:2.3:h:dahuasecurity:dvr0404hf-u-e |
| dahuasecurity | dvr0804 | cpe:2.3:h:dahuasecurity:dvr0804 |
| dahuasecurity | dvr0804hd-l | cpe:2.3:h:dahuasecurity:dvr0804hd-l |
| dahuasecurity | dvr0804hd-s | cpe:2.3:h:dahuasecurity:dvr0804hd-s |
| dahuasecurity | dvr0804hf-a-e | cpe:2.3:h:dahuasecurity:dvr0804hf-a-e |
and 53 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- dahuasecurity dvr0404hd-aall versions
- dahuasecurity dvr0404hd-lall versions
- dahuasecurity dvr0404hd-sall versions
- dahuasecurity dvr0404hd-uall versions
- dahuasecurity dvr0404hf-a-eall versions
- dahuasecurity dvr0404hf-al-eall versions
- dahuasecurity dvr0404hf-s-eall versions
- dahuasecurity dvr0404hf-u-eall versions
- dahuasecurity dvr0804all versions
- dahuasecurity dvr0804hd-lall versions
- dahuasecurity dvr0804hd-sall versions
- dahuasecurity dvr0804hf-a-eall versions
- dahuasecurity dvr0804hf-al-eall versions
- dahuasecurity dvr0804hf-l-eall versions
- dahuasecurity dvr0804hf-s-eall versions
- dahuasecurity dvr0804hf-u-eall versions
- dahuasecurity dvr1604hd-lall versions
- dahuasecurity dvr1604hd-sall versions
- dahuasecurity dvr1604hf-a-eall versions
- dahuasecurity dvr1604hf-al-eall versions
Same product
dahuasecurity: all recordsOther highest-scoring records for the same primary product.
- CVE-2013-5754The authorization implementation on Dahua DVR appliances accepts a hash string representing the current date for the role of a master passwo41Plan
- CVE-2013-3614Dahua DVR appliances have a small value for the maximum password length, which makes it easier for remote attackers to obtain access via a b39Monitor
- CVE-2013-3615Dahua DVR appliances use a password-hash algorithm with a short hash length, which makes it easier for context-dependent attackers to discov33Monitor
- CVE-2013-3613Dahua DVR appliances do not properly restrict UPnP requests, which makes it easier for remote attackers to obtain access via vectors involvi33Monitor
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
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | webapps | 2013-11-18 |
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.
- Published
- First PoC+62 d
- TodaySep 30, 2026+4762 d
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
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- C · data can be read
- Integrity
- C · data or configuration can be modified
- Availability
- C · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- C
- Integrity impact
- C
- Availability impact
- C
Weakness class (CWE)
CWE-255 · Credentials Management ErrorsCVSS vector
AV:N/AC:L/Au:N/C:C/I:C/A:C
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.
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.