# CVE-2018-11400: Security feature bypass in n/a

> A physically proximate attacker can bypass tamper detection by removing power sources without triggering notifications in the SimpliSafe Original Base Station.

- **Severity:** Medium 4.6 (`CVSS:3.0/AV:P/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:** 24 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8x45-65jf-g394

## What is CVE-2018-11400?

CVE-2018-11400 is a medium-severity vulnerability in n/a, published on 24 May 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In SimpliSafe Original, the Base Station fails to detect tamper attempts: it does not send a notification if a physically proximate attacker removes the battery and external power.

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

It affects 1 product.


Products: Simplisafe U9k-Bs1000 Firmware.

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

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

## Is CVE-2018-11400 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-11401](https://insights.sbomify.com/CVE-2018-11401/): In SimpliSafe Original, RF Interference (e.g., an extremely strong 433.92 MHz signal) by a physically proximate attacker does not cause a notification. (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-11400 is a medium-severity vulnerability in n/a, published on 24 May 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-11400 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-11400/ (Markdown: https://insights.sbomify.com/CVE-2018-11400/index.md)
```

## Sources

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

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