# CVE-2022-45434: Server-side request forgery in DSS Professional, DSS Express, DHI-DSS7016D-S2/DHI-DSS7016DR-S2, DHI-DSS4004-S2

> An attacker can force the Dahua DSS Server to launch ICMP attacks against designated targets, potentially causing denial of service or acting as a proxy.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/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:** 27 Dec 2022
- **Updated:** 14 Apr 2025
- **Also known as:** GHSA-824h-6hr6-ghh3

## What is CVE-2022-45434?

CVE-2022-45434 is a medium-severity server-side request forgery vulnerability in DSS Professional, DSS Express, DHI-DSS7016D-S2/DHI-DSS7016DR-S2, DHI-DSS4004-S2, published on 27 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Some Dahua software products have a vulnerability of unauthenticated un-throttled ICMP requests on remote DSS Server. After bypassing the firewall access control policy, by sending a specific crafted packet to the vulnerable interface, an attacker could exploit the victim server to launch ICMP request attack to the designated target host.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2022-45434?

It affects 5 products.


Products: Dahuasecurity Dhi-Dss4004-S2 Firmware, Dahuasecurity Dhi-Dss7016d-S2 Firmware, Dahuasecurity Dhi-Dss7016dr-S2 Firmware, Dahuasecurity Dss Express, Dahuasecurity Dss Professional.

## How do I fix CVE-2022-45434?

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

## Is CVE-2022-45434 being exploited?

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

## Other vulnerabilities in DSS Professional, DSS Express, DHI-DSS7016D-S2/DHI-DSS7016DR-S2, DHI-DSS4004-S2

- [CVE-2022-45423](https://insights.sbomify.com/CVE-2022-45423/): Information disclosure in DSS Professional, DSS Express, DHI-DSS7016D-S2/DHI-DSS7016DR-S2, DHI-DSS4004-S2 (high 7.5)
- [CVE-2022-45425](https://insights.sbomify.com/CVE-2022-45425/): Hardcoded credentials in DSS Professional, DSS Express, DHI-DSS7016D-S2/DHI-DSS7016DR-S2, DHI-DSS4004-S2 (high 7.5)
- [CVE-2022-45429](https://insights.sbomify.com/CVE-2022-45429/): Server-side request forgery in DSS Professional, DSS Express, DHI-DSS7016D-S2/DHI-DSS7016DR-S2, DHI-DSS4004-S2 (high 7.5)
- [CVE-2022-45431](https://insights.sbomify.com/CVE-2022-45431/): Auth bypass in DSS Professional, DSS Express, DHI-DSS7016D-S2/DHI-DSS7016DR-S2, DHI-DSS4004-S2 (high 7.5)
- [CVE-2022-45427](https://insights.sbomify.com/CVE-2022-45427/): File upload in DSS Professional, DSS Express, DHI-DSS7016D-S2/DHI-DSS7016DR-S2, DHI-DSS4004-S2 (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-45434 and fix it if it is affected.

What it is: CVE-2022-45434 is a medium-severity server-side request forgery vulnerability in DSS Professional, DSS Express, DHI-DSS7016D-S2/DHI-DSS7016DR-S2, DHI-DSS4004-S2, published on 27 Dec 2022. 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-2022-45434 in the wild and no public exploit code.

Affected product: DSS Professional, DSS Express, DHI-DSS7016D-S2/DHI-DSS7016DR-S2, DHI-DSS4004-S2. 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-2022-45434/ (Markdown: https://insights.sbomify.com/CVE-2022-45434/index.md)
```

## Sources

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

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