# CVE-2022-23382: Denial of service in n/a

> Attackers can cause denial of service on Hichip IP cameras by sending crafted multicast messages within the local network.

- **Severity:** High 8.1 (`CVSS:3.1/AC:L/AV:A/A:H/C:N/I:H/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2023
- **Updated:** 26 Sep 2024
- **Also known as:** GHSA-8x9q-p82f-q5gx

## What is CVE-2022-23382?

CVE-2022-23382 is a high-severity denial of service vulnerability in n/a, published on 11 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Shenzhen Hichip Vision Technology IP Camera Firmware V11.4.8.1.1-20170926 has a denial of service vulnerability through sending a crafted multicast message in a local network.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


Products: Hichip Shenzhen Hichip Vision Technology Firmware.

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

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

## Is CVE-2022-23382 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-23382 exists.

## Other vulnerabilities in n/a

- [CVE-2020-9527](https://insights.sbomify.com/CVE-2020-9527/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-9529](https://insights.sbomify.com/CVE-2020-9529/): Privilege escalation in n/a (critical 9.8)
- [CVE-2020-9528](https://insights.sbomify.com/CVE-2020-9528/): Weak cryptography in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-23382 is a high-severity denial of service vulnerability in n/a, published on 11 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-23382 exists.

Affected product: n/a. 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-23382/ (Markdown: https://insights.sbomify.com/CVE-2022-23382/index.md)
```

## Sources

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

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