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

> Attackers can disable Blink cameras and block video recording by disconnecting the Sync Module from Wi-Fi via deauthentication attacks.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jcr7-hfgj-536m

## What is CVE-2018-20161?

CVE-2018-20161 is a medium-severity denial of service vulnerability in n/a, published on 15 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A design flaw in the BlinkForHome (aka Blink For Home) Sync Module 2.10.4 and earlier allows attackers to disable cameras via Wi-Fi, because incident clips (triggered by the motion sensor) are not saved if the attacker's traffic (such as Dot11Deauth) successfully disconnects the Sync Module from the Wi-Fi network. (Access to live video from the app also becomes unavailable.)

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

It affects 1 product.


Products: Blinkforhome Sync Module.

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

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

## Is CVE-2018-20161 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-20161 is a medium-severity denial of service vulnerability in n/a, published on 15 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-20161 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-20161/ (Markdown: https://insights.sbomify.com/CVE-2018-20161/index.md)
```

## Sources

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

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