# CVE-2019-3997: Auth bypass in SimpliSafe SS3

> Local attackers can bypass authentication to pair rogue keypads with armed SimpliSafe SS3 systems, compromising physical security.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/A: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:** 16 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-xf4q-mw4x-gjfq

## What is CVE-2019-3997?

CVE-2019-3997 is a medium-severity authentication bypass vulnerability in SimpliSafe SS3, published on 16 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Authentication bypass using an alternate path or channel in SimpliSafe SS3 firmware 1.0-1.3 allows a local, unauthenticated attacker to pair a rogue keypad to an armed system.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2019-3997?

It affects 1 product.


Products: Simplisafe Ss3 Firmware.

## How do I fix CVE-2019-3997?

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

## Is CVE-2019-3997 being exploited?

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

## Other vulnerabilities in SimpliSafe SS3

- [CVE-2020-5727](https://insights.sbomify.com/CVE-2020-5727/): Auth bypass in SimpliSafe SS3 (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-3997 and fix it if it is affected.

What it is: CVE-2019-3997 is a medium-severity authentication bypass vulnerability in SimpliSafe SS3, published on 16 Jan 2020. 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-2019-3997 in the wild and no public exploit code.

Affected product: SimpliSafe SS3. 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-2019-3997/ (Markdown: https://insights.sbomify.com/CVE-2019-3997/index.md)
```

## Sources

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

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