# CVE-2019-9678: Denial of service in IPC-HDW1X2X,IPC-HFW1X2X,IPC-HDW2X2X,IPC-HFW2X2X,IPC-HDW4X2X,IPC-HFW4X2X,IPC-HDBW4X2X,IPC-HDW5X2X,IPC-HFW5X2X

> An attacker can crash Dahua IP cameras by sending a malicious packet during the login process, causing a denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 18 Sep 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-frg2-2p49-56f3

## What is CVE-2019-9678?

CVE-2019-9678 is a high-severity denial of service vulnerability in Dahua Technology IPC-HDW1X2X,IPC-HFW1X2X,IPC-HDW2X2X,IPC-HFW2X2X,IPC-HDW4X2X,IPC-HFW4X2X,IPC-HDBW4X2X,IPC-HDW5X2X,IPC-HFW5X2X, published on 18 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Some Dahua products have the problem of denial of service during the login process. An attacker can cause a device crashed by constructing a malicious packet. Affected products include: IPC-HDW1X2X,IPC-HFW1X2X,IPC-HDW2X2X,IPC-HFW2X2X,IPC-HDW4X2X,IPC-HFW4X2X,IPC-HDBW4X2X,IPC-HDW5X2X,IPC-HFW5X2X for versions which Build time is before August 18, 2019.

## Which versions are affected by CVE-2019-9678?

It affects 9 products.


Products: Dahuasecurity Ipc-Hdbw4x2x Firmware, Dahuasecurity Ipc-Hdw1x2x Firmware, Dahuasecurity Ipc-Hdw2x2x Firmware, Dahuasecurity Ipc-Hdw4x2x Firmware, Dahuasecurity Ipc-Hdw5x2x Firmware, Dahuasecurity Ipc-Hfw1x2x Firmware, Dahuasecurity Ipc-Hfw2x2x Firmware, Dahuasecurity Ipc-Hfw4x2x Firmware, Dahuasecurity Ipc-Hfw5x2x Firmware.

## How do I fix CVE-2019-9678?

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

## Is CVE-2019-9678 being exploited?

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

## Other vulnerabilities in Dahua Technology IPC-HDW1X2X,IPC-HFW1X2X,IPC-HDW2X2X,IPC-HFW2X2X,IPC-HDW4X2X,IPC-HFW4X2X,IPC-HDBW4X2X,IPC-HDW5X2X,IPC-HFW5X2X

- [CVE-2019-9677](https://insights.sbomify.com/CVE-2019-9677/): Memory corruption in IPC-HDW1X2X,IPC-HFW1X2X,IPC-HDW2X2X,IPC-HFW2X2X,IPC-HDW4X2X,IPC-HFW4X2X,IPC-HDBW4X2X,IPC-HDW5X2X,IPC-HFW5X2X (critical 9.8)
- [CVE-2019-9679](https://insights.sbomify.com/CVE-2019-9679/): Missing authorization in IPC-HDW1X2X,IPC-HFW1X2X,IPC-HDW2X2X,IPC-HFW2X2X,IPC-HDW4X2X,IPC-HFW4X2X,IPC-HDBW4X2X,IPC-HDW5X2X,IPC-HFW5X2X (high 8.8)
- [CVE-2019-9680](https://insights.sbomify.com/CVE-2019-9680/): Information disclosure in IPC-HDW1X2X,IPC-HFW1X2X,IPC-HDW2X2X,IPC-HFW2X2X,IPC-HDW4X2X,IPC-HFW4X2X,IPC-HDBW4X2X,IPC-HDW5X2X,IPC-HFW5X2X (medium 5.3)
- [CVE-2019-9681](https://insights.sbomify.com/CVE-2019-9681/): Information disclosure in IPC-HDW1X2X,IPC-HFW1X2X,IPC-HDW2X2X,IPC-HFW2X2X,IPC-HDW4X2X,IPC-HFW4X2X,IPC-HDBW4X2X,IPC-HDW5X2X,IPC-HFW5X2X (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-9678 and fix it if it is affected.

What it is: CVE-2019-9678 is a high-severity denial of service vulnerability in Dahua Technology IPC-HDW1X2X,IPC-HFW1X2X,IPC-HDW2X2X,IPC-HFW2X2X,IPC-HDW4X2X,IPC-HFW4X2X,IPC-HDBW4X2X,IPC-HDW5X2X,IPC-HFW5X2X, published on 18 Sep 2019. 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-2019-9678 in the wild and no public exploit code.

Affected product: Dahua Technology IPC-HDW1X2X,IPC-HFW1X2X,IPC-HDW2X2X,IPC-HFW2X2X,IPC-HDW4X2X,IPC-HFW4X2X,IPC-HDBW4X2X,IPC-HDW5X2X,IPC-HFW5X2X. 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-2019-9678/ (Markdown: https://insights.sbomify.com/CVE-2019-9678/index.md)
```

## Sources

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

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