CVE-2021-33045: The identity authentication bypass vulnerability found in some Dahua products during the login process.
Noroxi assessment
Priority: Now (action score 99/100)
- CISA has confirmed exploitation in the wild (Aug 21, 2024). Remediation deadline for US federal agencies: Sep 11, 2024.
- A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
- Probability of exploitation in the next 30 days: 99.5% (FIRST EPSS); higher than 99.9% 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 CISA the attack is automatable: targets can be found by mass scanning.
- According to the record, no fixed version is available yet.
Patch today or shut off access. Until a fix is released, restrict access to the affected component and 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 · CISA KEV · FIRST EPSS
The identity authentication bypass vulnerability found in some Dahua products during the login process. Attackers can bypass device identity authentication by constructing malicious data packets.
- Published
- Sep 15, 2021
- Updated
- Jun 16, 2026
- EPSS
- 99.5% · 99th percentile
- CWE
- CWE-287
Report tools
Action score
99
Now
Patch today or shut off access.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 30 / 30 · Listed
- EPSS
- 30 / 30 · 99.5%
CISA SSVC decision
- Exploitation
- active
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Actively exploited in the wild
CISA added this to its Known Exploited Vulnerabilities catalog on Aug 21, 2024. That signals real attacks, not theory.
Remediation deadline for US federal agencies: Sep 11, 2024.
Get told when this record changes
- In CISA KEV: exploitation in the wild confirmed
- Weaponized exploit exists
- 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-hum7xxx firmware | cpe:2.3:o:dahuasecurity:ipc-hum7xxx_firmware |
| dahuasecurity | ipc-hum7xxx | cpe:2.3:h:dahuasecurity:ipc-hum7xxx |
| dahuasecurity | ipc-hx3xxx firmware | cpe:2.3:o:dahuasecurity:ipc-hx3xxx_firmware |
| dahuasecurity | ipc-hx3xxx | cpe:2.3:h:dahuasecurity:ipc-hx3xxx |
| dahuasecurity | ipc-hx5xxx firmware | cpe:2.3:o:dahuasecurity:ipc-hx5xxx_firmware |
| dahuasecurity | ipc-hx5xxx | cpe:2.3:h:dahuasecurity:ipc-hx5xxx |
| dahuasecurity | nvr-1xxx firmware | cpe:2.3:o:dahuasecurity:nvr-1xxx_firmware |
| dahuasecurity | nvr-1xxx | cpe:2.3:h:dahuasecurity:nvr-1xxx |
| dahuasecurity | nvr-2xxx firmware | cpe:2.3:o:dahuasecurity:nvr-2xxx_firmware |
| dahuasecurity | nvr-2xxx | cpe:2.3:h:dahuasecurity:nvr-2xxx |
| dahuasecurity | nvr-4xxx firmware | cpe:2.3:o:dahuasecurity:nvr-4xxx_firmware |
| dahuasecurity | nvr-4xxx | cpe:2.3:h:dahuasecurity:nvr-4xxx |
and 24 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- dahuasecurity ipc-hum7xxx firmwarebefore 2.820.0000000.5.r.210705
- dahuasecurity ipc-hx3xxx firmwarebefore 2.800.0000000.29.r.210630
- dahuasecurity ipc-hx5xxx firmwarebefore 2.820.0000000.5.r.210705
- dahuasecurity nvr-1xxx firmwarebefore 4.001.0000005.1.r.210709
- dahuasecurity nvr-2xxx firmwarebefore 4.001.0000000.1.r.210710
- dahuasecurity nvr-4xxx firmwarebefore 4.001.0000005.1.r.210713
- dahuasecurity nvr-5xxx firmwarebefore 4.001.0000000.0.r.210710
- dahuasecurity nvr-6xx firmwarebefore 4.001.0000001.1.r.210716
- dahuasecurity vth-542xh firmwarebefore 4.500.0000002.0.r.210715
- dahuasecurity vto-65xxx firmwarebefore 4.300.0000004.0.r.210715
- dahuasecurity vto-75x95x firmwarebefore 4.300.0000003.0.r.210714
- dahuasecurity xvr-4x04 firmwareall versions
- dahuasecurity xvr-4x04 firmwarebefore 4.001.0000001.1.r.210709
- dahuasecurity xvr-4x08 firmwarebefore 4.001.0000001.1.r.210709
- dahuasecurity xvr-5x04 firmwarebefore 4.001.0000003.1.r.210710
- dahuasecurity xvr-5x08 firmwarebefore 4.001.0000003.1.r.210710
- dahuasecurity xvr-5x16 firmwarebefore 4.001.0000003.1.r.210710
- dahuasecurity xvr-7x16 firmwarebefore 4.001.0000003.1.r.210710
- dahuasecurity xvr-7x32 firmwarebefore 4.001.0000003.1.r.210710
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 Some Dahua IP Camera, Video Intercom, NVR, XVR devices
- Dahua IP Camera devices IPC-HX3XXX, IPC-HX5XXX, and IPC-HUM7XXX Buildtime before May, 2020, Video Intercom devices VTO75X95X, VTO65XXX, and VTH542XH, NVR devices NVR1XXX, NVR2XXX, NVR5XXX, and NVR6XX,affected
Same product
dahuasecurity: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-33044The identity authentication bypass vulnerability found in some Dahua products during the login process.KEV99Now
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
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Nuclei detection template ×1
- Proof-of-concept repository on GitHub ×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 |
|---|---|---|
| Nuclei detection template | Nuclei template CVE-2021-33045 | — |
| Proof-of-concept repository on GitHub | stars:9 | 2021-10-11 |
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+25 d
- CISA KEV+1070 d
- TodayOct 31, 2026+1872 d
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 (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.