CVE-2021-21736
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 · uneditedA smart camera product of ZTE is impacted by a permission and access control vulnerability. Due to the defect of user permission management by the cloud-end app, users whose sharing permissions have been revoked can still control the camera, such as restarting the camera, restoring factory settings, etc.. This affects ZXHN HS562 V1.0.0.0B2.0000, V1.0.0.0B3.0000E
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 confidenceThe ZXHN HS562 smart camera has a permission management flaw in its cloud-end application. When a user's sharing permissions are revoked through the cloud interface, the revocation is not properly propagated to the camera's control layer, allowing previously authorized users to still send control commands like restart and factory reset.
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= 1.0.0.0b2.0000= 1.0.0.0b3.0000CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 the camera firmware versionAccess the camera's web interface or administrative panel and navigate to the System Settings or About section to view the firmware version. Alternatively, use the camera's mobile app or check the device label for the firmware build number.Affected if The firmware version is 1.0.0.0b2.0000 or 1.0.0.0b3.0000
-
Determine if cloud sharing is enabledCheck the camera's mobile app or web interface for the cloud sharing or user sharing feature configuration. Look for any active shares where the camera is linked to a cloud account with other users granted access.Affected if Cloud sharing is configured and the camera has multiple users or accounts with access permissions
-
Review camera access logs for control commandsAccess the camera's administrative interface or cloud management portal to view access logs or event history. Look for commands such as restart, factory reset, or device configuration changes.Affected if Control commands appear in logs from user accounts that were previously granted access but later revoked through the cloud interface
-
Verify current allowed users against expected permissionsCompare the list of users currently permitted to access the camera (found in camera settings or cloud management) against records of users who should have had access revoked.Affected if Users who were revoked through the cloud interface still appear in the camera's allowed users list or are still able to send control commands
A user is affected if the camera runs firmware version 1.0.0.0b2.0000 or 1.0.0.0b3.0000, cloud sharing was configured, and control commands can still be issued by users who were revoked through the cloud interface.
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 dataApply vendor-provided firmware updates for ZXHN HS562 V1.0.0.0B2.0000 and V1.0.0.0B3.0000E. Until patched, monitor camera access logs for unauthorized control commands from revoked users.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21736 — 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-21736 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