CVE-2017-9315
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 · uneditedCustomer of Dahua IP camera or IP PTZ could submit relevant device information to receive a time limited temporary password from Dahua authorized dealer to reset the admin password. The algorithm used in this mechanism is potentially at risk of being compromised and subsequently utilized by attacker.
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 IP cameras and IP PTZ devices contain a vulnerability in the temporary password reset mechanism. An attacker who obtains device information (such as serial number, MAC address, or other identifiers) could potentially compromise the algorithm used to generate time-limited temporary passwords, allowing unauthorized admin password reset and device takeover.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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.0/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 the camera model and firmware versionAccess the camera's web interface or use ONVIF/SDK tools to query the device information. Look for the model number (Hfw1xxx, Hdw1xxx, Hdbw1xxx, Hfw2xxx, Hdw2xxx, Hdbw2xxx, Hfw4xxx, Hdw4xxx series) and firmware version in the system information or device status page.Affected if The device is a Dahua IP camera from any of the Hfw1xxx, Hdw1xxx, Hdbw1xxx, Hfw2xxx, Hdw2xxx, Hdbw2xxx, Hfw4xxx, or Hdw4xxx series, as all firmware versions in these series are affected.
-
Determine if the device is network accessibleCheck if the camera management interface (typically ports 80, 443, or 37777) is exposed to untrusted networks. Use network scanning tools or check firewall rules to see if the device is reachable from outside the local network.Affected if The camera is directly accessible from untrusted networks, which would allow an attacker to obtain device identifiers and attempt the temporary password reset exploit.
-
Verify if password reset functionality is enabledAccess the camera's web interface and navigate to the user management or password settings section. Check if the temporary password reset feature or password recovery mechanism is enabled or available.Affected if The temporary password reset mechanism is enabled, allowing an attacker who obtains device identifiers (serial number, MAC address) to potentially generate a valid temporary password.
-
Review device logs for password reset attemptsExamine the camera's system logs, security logs, or event logs for any password reset requests, especially those originating from external IP addresses or occurring at unusual times.Affected if There are unauthorized password reset requests in the logs, indicating potential exploitation attempts of this vulnerability.
You are affected if you have a Dahua IP camera from the Hfw1xxx, Hdw1xxx, Hdbw1xxx, Hfw2xxx, Hdw2xxx, Hdbw2xxx, Hfw4xxx, or Hdw4xxx series with network-accessible management interface and the temporary password reset feature enabled.
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 access to camera management interfaces, monitor for suspicious password reset requests, and apply vendor firmware updates when available. Consider implementing additional authentication layers such as VPN access for device management.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9315 — 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-2017-9315 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