CVE-2021-33046: Some Dahua products have access control vulnerability in the password reset process.
Noroxi assessment
Priority: Monitor (action score 39/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: 1.3% (FIRST EPSS); higher than 71.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is 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
Some Dahua products have access control vulnerability in the password reset process. Attackers can exploit this vulnerability through specific deployments to reset device passwords.
- Published
- Jan 13, 2022
- Updated
- Jun 16, 2026
- EPSS
- 1.3% · 71th percentile
- CWE
- CWE-287
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.3%
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 | ipc-hx1xxx firmware | cpe:2.3:o:dahuasecurity:ipc-hx1xxx_firmware |
| dahuasecurity | ipc-hx1xxx | cpe:2.3:h:dahuasecurity:ipc-hx1xxx |
| dahuasecurity | ipc-hx2xxx firmware | cpe:2.3:o:dahuasecurity:ipc-hx2xxx_firmware |
| dahuasecurity | ipc-hx2xxx | cpe:2.3:h:dahuasecurity:ipc-hx2xxx |
| dahuasecurity | ipc-hx3xxx firmware | cpe:2.3:o:dahuasecurity:ipc-hx3xxx_firmware |
| dahuasecurity | ipc-hx3xxx | cpe:2.3:h:dahuasecurity:ipc-hx3xxx |
| dahuasecurity | ipc-hx5\(4\)\(3\)xxx firmware | cpe:2.3:o:dahuasecurity:ipc-hx5\(4\)\(3\)xxx_firmware |
| dahuasecurity | ipc-hx5\(4\)\(3\)xxx | cpe:2.3:h:dahuasecurity:ipc-hx5\(4\)\(3\)xxx |
| dahuasecurity | ipc-hx5xxx firmware | cpe:2.3:o:dahuasecurity:ipc-hx5xxx_firmware |
| dahuasecurity | ipc-hx5xxx | cpe:2.3:h:dahuasecurity:ipc-hx5xxx |
| dahuasecurity | sd1a1 firmware | cpe:2.3:o:dahuasecurity:sd1a1_firmware |
| dahuasecurity | sd1a1 | cpe:2.3:h:dahuasecurity:sd1a1 |
and 44 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- dahuasecurity asc2204c firmware2017-7 and later · up to 2021-7 inclusive
- dahuasecurity hcvr7xxx firmware2017-7 and later · up to 2021-7 inclusive
- dahuasecurity hcvr8xxx firmware2017-7 and later · up to 2021-7 inclusive
- dahuasecurity ipc-hx1xxx firmware2017-7 and later · up to 2021-7 inclusive
- dahuasecurity ipc-hx2xxx firmware2017-7 and later · up to 2021-7 inclusive
- dahuasecurity ipc-hx3xxx firmware2017-7 and later · up to 2021-7 inclusive
- dahuasecurity ipc-hx5(4)(3)xxx firmware2017-7 and later · up to 2021-7 inclusive
- dahuasecurity ipc-hx5xxx firmware2017-7 and later · up to 2021-7 inclusive
- dahuasecurity nvr1xxx firmware2017-7 and later · up to 2021-7 inclusive
- dahuasecurity nvr2xxx firmware2017-7 and later · up to 2021-7 inclusive
- dahuasecurity nvr4xxx firmware2017-7 and later · up to 2021-7 inclusive
- dahuasecurity nvr5xxx firmware2017-7 and later · up to 2021-7 inclusive
- dahuasecurity sd1a1 firmware2017-7 and later · up to 2021-7 inclusive
- dahuasecurity sd22 firmware2017-7 and later · up to 2021-7 inclusive
- dahuasecurity sd49 firmware2017-7 and later · up to 2021-7 inclusive
- dahuasecurity sd50 firmware2017-7 and later · up to 2021-7 inclusive
- dahuasecurity sd52c firmware2017-7 and later · up to 2021-7 inclusive
- dahuasecurity sd6al firmware2017-7 and later · up to 2021-7 inclusive
- dahuasecurity tpc-bf1241 firmware2017-7 and later · up to 2021-7 inclusive
- dahuasecurity tpc-bf2221 firmware2017-7 and later · up to 2021-7 inclusive
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 Access control vulnerability found in some Dahua products
- Dahua IP Camera devices IPC-HX3XXX, and IPC-HX5XXX, PTZ Dome Camera SD1A1, SD22, SD49, SD50, SD52C, and SD6AL, Thermal TPC-BF1241,TPC-BF2221, TPC-SD2221, VTO2101E, VTOX221E, and ASC2204C devices Buildtime between 2017/7 ~ 2021/7. NVR devices NVR4XXX, and NVR5XXX, XVR devices XVR4XXX, and XVR5XXX, HCVR devices HCVR7XXX, and HCVR8XXX devices Buildtime between 2017/1 ~ 2021/7.affected
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.
No history yet (it accumulates with the daily EPSS job).
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.
- No special conditions are required; it is repeatable.
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
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middleware
app.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();
admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);
app.use("/admin", admin);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)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.