dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 26 Mar 2026.
Ds 2cd2032 I FirmwareOperating system · Hikvision

CVE-2017-7921

CRITICAL · 9.8 CVSS v3.1 Published 2017-05-06
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Zero-click Patch available

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 · unedited
An Improper Authentication issue was discovered in Hikvision DS-2CD2xx2F-I Series V5.2.0 build 140721 to V5.4.0 build 160530, DS-2CD2xx0F-I Series V5.2.0 build 140721 to V5.4.0 Build 160401, DS-2CD2xx2FWD Series V5.3.1 build 150410 to V5.4.4 Build 161125, DS-2CD4x2xFWD Series V5.2.0 build 140721 to V5.4.0 Build 160414, DS-2CD4xx5 Series V5.2.0 build 140721 to V5.4.0 Build 160421, DS-2DFx Series V5.2.0 build 140805 to V5.4.5 Build 160928, and DS-2CD63xx Series V5.0.9 build 140305 to V5.3.5 Build 160106 devices. The improper authentication vulnerability occurs when an application does not adequately or correctly authenticate users. This may allow a malicious user to escalate his or her privileges on the system and gain access to sensitive information.

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 · high confidence

This is an authentication bypass vulnerability in Hikvision IP cameras (multiple series listed) that allows unauthenticated attackers to gain administrative access by exploiting improper authentication checks, potentially exposing sensitive video feeds and system controls.

MitigationUpdate affected Hikvision devices to patched firmware versions beyond the vulnerable builds listed. If updates are unavailable, implement network segmentation and restrict access to camera management interfaces.

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
Ds 2cd2032 I FirmwareOperating system
Affected:all versions
Ds 2cd2112 I FirmwareOperating system
Affected:all versions
Ds 2cd2132 I FirmwareOperating system
Affected:all versions
Ds 2cd2212 I5 FirmwareOperating system
Affected:all versions
Ds 2cd2232 I5 FirmwareOperating system
Affected:all versions
Ds 2cd2312 I FirmwareOperating system
Affected:all versions
Ds 2cd2332 I FirmwareOperating system
Affected:all versions
Ds 2cd2412f I\(w\) FirmwareOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Hikvision camera model
    Access the camera web interface or check the device label/metadata to determine the exact model number (e.g., DS-2CD2032-I, DS-2CD2112-I, DS-2CD2132-I, DS-2CD2212-I5, DS-2CD2232-I5, DS-2CD2312-I, DS-2CD2332-I, DS-2CD2412F-I(W))
    Affected if The model matches any of the following: DS-2CD2032-I, DS-2CD2112-I, DS-2CD2132-I, DS-2CD2212-I5, DS-2CD2232-I5, DS-2CD2312-I, DS-2CD2332-I, or DS-2CD2412F-I(W)
  2. Confirm the firmware version
    Log into the camera web interface and navigate to the System or Maintenance section to view the installed firmware version
    Affected if Any firmware version is installed (all versions of the listed models are affected)
  3. Check network accessibility
    Verify if the camera is accessible over the network by attempting to reach its IP address on HTTP (port 80) or HTTPS (port 443) from an external or unauthorized network segment
    Affected if The camera is reachable from network segments that should not have access, indicating potential exposure to unauthorized users
  4. Verify authentication behavior
    Attempt to access camera endpoints or APIs without providing valid credentials to observe if authentication is properly enforced
    Affected if The device allows access or returns sensitive information without requiring valid authentication credentials

You are affected if you have any of the listed Hikvision camera models (DS-2CD2xxx series) running on your network, as all firmware versions contain the authentication bypass vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www.hikvision.com →
Interim mitigation

Update affected Hikvision devices to patched firmware versions beyond the vulnerable builds listed. If updates are unavailable, implement network segmentation and restrict access to camera management interfaces.

Recommended fix Moderate confidence

Hikvision has released patched firmware versions beyond V5.4.5 (for affected series). Obtain the specific fixed version for your model from Hikvision's official security advisory.

  1. 1. Identify the exact model number and current firmware version of the Hikvision device by accessing the device's web interface or using the Hikvision SADP tool.
  2. 2. Consult the official Hikvision security advisory at www.hikvision.com for the specific fixed firmware version corresponding to your device model.
  3. 3. Download the firmware update only from the official Hikvision website to ensure authenticity.
  4. 4. Back up the device configuration before performing the firmware upgrade.
  5. 5. Follow Hikvision's official firmware upgrade instructions, typically accessed through the device web interface or Hikvision IVMS software.
  6. 6. After upgrading, verify the firmware version has been successfully updated and test authentication functionality.
  7. 7. Change default administrator credentials immediately after the upgrade if not already done.
Caveat Firmware upgrades may reset device configuration to defaults; backup configuration before upgrading. Some legacy features may be deprecated in newer firmware versions.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ds 2cd2032 I Firmware Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-7921 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-7921 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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