# CVE-2017-9315: Auth bypass in Dahua IP Camera and IP PTZ IPC-HFW1XXX, IPC-HDW1XXX, IPC-HDBW1XXX, IPC-HFW2XXX, IPC-HDW2XXX, IPC-HDBW2XXX, IPC-HFW4XXX, IPC-HDW4XXX, IPC-HDBW4XXX, IPC-HF5XXX, IPC-HFW5XXX, IPC-HDW5XXX, IPC-HDBW5XXX, IPC-HF8XXX, IPC-HFW8XXX, IPC-HDBW8XXX, IPC-EBW8XXX, IPC-PFW8xxx, IPC-PDBW8xxx, IPC-HUM8xxx, PSD8xxxx, DH-SD2XXXXX, DH-SD4XXXXX, DH-SD5XXXXX, DH-SD6XXXXX

> Attackers can compromise the temporary password reset algorithm to gain unauthorized admin access to Dahua IP cameras and PTZ devices.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Nov 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-hcw2-qh59-gg8h

## What is CVE-2017-9315?

CVE-2017-9315 is a critical authentication bypass vulnerability in Dahua IP Camera and IP PTZ IPC-HFW1XXX, IPC-HDW1XXX, IPC-HDBW1XXX, IPC-HFW2XXX, IPC-HDW2XXX, IPC-HDBW2XXX, IPC-HFW4XXX, IPC-HDW4XXX, IPC-HDBW4XXX, IPC-HF5XXX, IPC-HFW5XXX, IPC-HDW5XXX, IPC-HDBW5XXX, IPC-HF8XXX, IPC-HFW8XXX, IPC-HDBW8XXX, IPC-EBW8XXX, IPC-PFW8xxx, IPC-PDBW8xxx, IPC-HUM8xxx, PSD8xxxx, DH-SD2XXXXX, DH-SD4XXXXX, DH-SD5XXXXX, DH-SD6XXXXX, published on 28 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Customer 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.

## Which versions are affected by CVE-2017-9315?

It affects 25 products.


Products: Dahuasecurity Dh-Sd2xxxxx Firmware, Dahuasecurity Dh-Sd4xxxxx Firmware, Dahuasecurity Dh-Sd5xxxxx Firmware, Dahuasecurity Dh-Sd6xxxxx Firmware, Dahuasecurity Ipc-Ebw8xxx Firmware, Dahuasecurity Ipc-Hdbw1xxx Firmware, Dahuasecurity Ipc-Hdbw2xxx Firmware, Dahuasecurity Ipc-Hdbw4xxx Firmware, Dahuasecurity Ipc-Hdbw5xxx Firmware, Dahuasecurity Ipc-Hdbw8xxx Firmware, Dahuasecurity Ipc-Hdw1xxx Firmware, Dahuasecurity Ipc-Hdw2xxx Firmware, Dahuasecurity Ipc-Hdw4xxx Firmware, Dahuasecurity Ipc-Hdw5xxx Firmware, Dahuasecurity Ipc-Hf5xxx Firmware, Dahuasecurity Ipc-Hf8xxx Firmware, Dahuasecurity Ipc-Hfw1xxx Firmware, Dahuasecurity Ipc-Hfw2xxx Firmware, Dahuasecurity Ipc-Hfw4xxx Firmware, Dahuasecurity Ipc-Hfw5xxx Firmware and 5 more.

## How do I fix CVE-2017-9315?

No fix has been published for CVE-2017-9315 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-9315 being exploited?

There is no known exploitation of CVE-2017-9315 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9315 and fix it if it is affected.

What it is: CVE-2017-9315 is a critical authentication bypass vulnerability in Dahua IP Camera and IP PTZ IPC-HFW1XXX, IPC-HDW1XXX, IPC-HDBW1XXX, IPC-HFW2XXX, IPC-HDW2XXX, IPC-HDBW2XXX, IPC-HFW4XXX, IPC-HDW4XXX, IPC-HDBW4XXX, IPC-HF5XXX, IPC-HFW5XXX, IPC-HDW5XXX, IPC-HDBW5XXX, IPC-HF8XXX, IPC-HFW8XXX, IPC-HDBW8XXX, IPC-EBW8XXX, IPC-PFW8xxx, IPC-PDBW8xxx, IPC-HUM8xxx, PSD8xxxx, DH-SD2XXXXX, DH-SD4XXXXX, DH-SD5XXXXX, DH-SD6XXXXX, published on 28 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-9315 in the wild and no public exploit code.

Affected product: Dahua IP Camera and IP PTZ IPC-HFW1XXX, IPC-HDW1XXX, IPC-HDBW1XXX, IPC-HFW2XXX, IPC-HDW2XXX, IPC-HDBW2XXX, IPC-HFW4XXX, IPC-HDW4XXX, IPC-HDBW4XXX, IPC-HF5XXX, IPC-HFW5XXX, IPC-HDW5XXX, IPC-HDBW5XXX, IPC-HF8XXX, IPC-HFW8XXX, IPC-HDBW8XXX, IPC-EBW8XXX, IPC-PFW8xxx, IPC-PDBW8xxx, IPC-HUM8xxx, PSD8xxxx, DH-SD2XXXXX, DH-SD4XXXXX, DH-SD5XXXXX, DH-SD6XXXXX. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-9315/ (Markdown: https://insights.sbomify.com/CVE-2017-9315/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-9315
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-9315
- OSV: https://osv.dev/vulnerability/CVE-2017-9315

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-9315/
Summaries are generated and may contain mistakes; the official description above is the record.