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

> Attackers can cause a denial of service by rebooting the device via a crafted application sending data to WifiService.

- **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:** 8 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fwjc-xwf7-mvwp

## What is CVE-2018-19980?

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

### Official description

Anker Nebula Capsule Pro NBUI_M1_V2.1.9 devices allow attackers to cause a denial of service (reboot of the underlying Android 7.1.2 operating system) via a crafted application that sends data to WifiService.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Anker Nebula Capsule Projector, Anker Nebula Capsule Projector Firmware.

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

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

## Is CVE-2018-19980 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-19980 is a high-severity denial of service vulnerability in n/a, published on 8 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-19980 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-19980/ (Markdown: https://insights.sbomify.com/CVE-2018-19980/index.md)
```

## Sources

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

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