# CVE-2019-9682: Weak cryptography in IPC-HX2XXX Series,IPC-HXXX5X4X Series,IPC-HX5842H,IPC-HX7842H,NVR 5x Series,NVR 4x Series,SD6AL Series,SD5A Series,SD1A Series,PTZ1A Series,SD50/52C Series,IPC-HDBW1320E-W

> Attackers can intercept network packets to compromise devices if users enable the optional weak security login mode.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 13 May 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-26hg-8v7r-7fj4

## What is CVE-2019-9682?

CVE-2019-9682 is a high-severity vulnerability in IPC-HX2XXX Series,IPC-HXXX5X4X Series,IPC-HX5842H,IPC-HX7842H,NVR 5x Series,NVR 4x Series,SD6AL Series,SD5A Series,SD1A Series,PTZ1A Series,SD50/52C Series,IPC-HDBW1320E-W, published on 13 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dahua devices with Build time before December 2019 use strong security login mode by default, but in order to be compatible with the normal login of early devices, some devices retain the weak security login mode that users can control. If the user uses a weak security login method, an attacker can monitor the device network to intercept network packets to attack the device. So it is recommended that the user disable this login method.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 20 products.


Products: Dahuasecurity Ipc-Hdbw1320e-W Firmware, Dahuasecurity Ipc-Hx2xxx Firmware, Dahuasecurity Ipc-Hx5842h Firmware, Dahuasecurity Ipc-Hx7842h Firmware, Dahuasecurity Ipc-Hxxx5x4x Firmware, Dahuasecurity N42b1p Firmware, Dahuasecurity N42b2p Firmware, Dahuasecurity N42b3p Firmware, Dahuasecurity N52a4p Firmware, Dahuasecurity N52b2p Firmware, Dahuasecurity N52b3p Firmware, Dahuasecurity N52b5p Firmware, Dahuasecurity N54a4p Firmware, Dahuasecurity N54b2p Firmware, Dahuasecurity Ptz1a Firmware, Dahuasecurity Sd1a Firmware, Dahuasecurity Sd50 Firmware, Dahuasecurity Sd52c Firmware, Dahuasecurity Sd5a Firmware, Dahuasecurity Sd6al Firmware.

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

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

## Is CVE-2019-9682 being exploited?

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

## Other vulnerabilities in IPC-HX2XXX Series,IPC-HXXX5X4X Series,IPC-HX5842H,IPC-HX7842H,NVR 5x Series,NVR 4x Series,SD6AL Series,SD5A Series,SD1A Series,PTZ1A Series,SD50/52C Series,IPC-HDBW1320E-W

- [CVE-2020-9502](https://insights.sbomify.com/CVE-2020-9502/): Auth bypass in IPC-HX2XXX Series,IPC-HXXX5X4X Series,IPC-HX5842H,IPC-HX7842H,NVR 5x Series,NVR 4x Series,SD6AL Series,SD5A Series,SD1A Series,PTZ1A Series,SD50/52C Series,IPC-HFW1431S (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-9682 is a high-severity vulnerability in IPC-HX2XXX Series,IPC-HXXX5X4X Series,IPC-HX5842H,IPC-HX7842H,NVR 5x Series,NVR 4x Series,SD6AL Series,SD5A Series,SD1A Series,PTZ1A Series,SD50/52C Series,IPC-HDBW1320E-W, published on 13 May 2020. 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-9682 in the wild and no public exploit code.

Affected product: IPC-HX2XXX Series,IPC-HXXX5X4X Series,IPC-HX5842H,IPC-HX7842H,NVR 5x Series,NVR 4x Series,SD6AL Series,SD5A Series,SD1A Series,PTZ1A Series,SD50/52C Series,IPC-HDBW1320E-W. 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-9682/ (Markdown: https://insights.sbomify.com/CVE-2019-9682/index.md)
```

## Sources

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

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