CVE-2021-33046
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSome Dahua products have access control vulnerability in the password reset process. Attackers can exploit this vulnerability through specific deployments to reset device passwords.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceDahua devices contain an access control vulnerability in the password reset function that allows unauthenticated attackers to reset device administrator passwords. The vulnerability is exploitable through specific network deployments and rates 9.8 due to network exploitability and complete loss of authentication control.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2017-7, <= 2021-7>= 2017-7, <= 2021-7>= 2017-7, <= 2021-7>= 2017-7, <= 2021-7>= 2017-7, <= 2021-7>= 2017-7, <= 2021-7>= 2017-7, <= 2021-7>= 2017-7, <= 2021-7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Dahua device model on the networkUse network scanning tools (e.g., nmap, Angry IP Scanner) or check device documentation to identify if any device matches the affected models: IPC Hx1xxx, Hx2xxx, Hx3xxx, Hx5(4)(3)xxx, Hx5xxx, SD1a1, SD22, or SD49Affected if The device is a Dahua IPC or SD series model from the list
-
Check the installed firmware versionAccess the device web interface or use SNMP/ONVIF to query the firmware version. Compare the version date against the affected range: >= 2017-7 and <= 2021-7Affected if The firmware version falls within July 2017 to July 2021 inclusive
-
Verify network exposure of the device management interfaceReview firewall rules and network segmentation to determine if the device HTTP/HTTPS ports (typically 80/443) are reachable from untrusted networks or the internetAffected if The device management interface is accessible from unauthenticated or external networks
-
Confirm password reset functionality is enabledCheck the device security settings via web interface or API to verify if the password reset feature is active (this is typically enabled by default on affected versions)Affected if Password reset functionality remains enabled on the device
You are affected if you have a Dahua IPC or SD device with firmware between July 2017 and July 2021 that is accessible from networks where unauthenticated attackers could reach the password reset function.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict network exposure of affected devices, implement firewall rules limiting access to management interfaces, check Dahua vendor advisories for firmware patches, and monitor for unauthorized password reset attempts.
- Consultation8.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,608.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-33046 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-33046 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data