# CVE-2018-20051: Denial of service in n/a

> Remote attackers can crash and reboot Jooan Wi-Fi cameras by sending malformed ONVIF requests, causing service disruption.

- **Severity:** High 7.5 (`CVSS:3.0/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:** 10 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-63wg-rrpw-6rxq

## What is CVE-2018-20051?

CVE-2018-20051 is a high-severity denial of service vulnerability in n/a, published on 10 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mishandling of '>' on the Jooan JA-Q1H Wi-Fi camera with firmware 21.0.0.91 allows remote attackers to cause a denial of service (crash and reboot) via certain ONVIF methods such as CreateUsers, SetImagingSettings, GetStreamUri, and so on.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-20051?

It affects 1 product.


Products: Qacctv Jooan Ja-Q1h Wi-Fi Camera Firmware.

## How do I fix CVE-2018-20051?

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

## Is CVE-2018-20051 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-20050](https://insights.sbomify.com/CVE-2018-20050/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-20051 and fix it if it is affected.

What it is: CVE-2018-20051 is a high-severity denial of service vulnerability in n/a, published on 10 Dec 2018. 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-2018-20051 in the wild and no public exploit code.

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-2018-20051/ (Markdown: https://insights.sbomify.com/CVE-2018-20051/index.md)
```

## Sources

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

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