# CVE-2017-17435: An issue was discovered in the software on Vaultek Gun Safe VT20i products, aka BlueSteal.


- **Severity:** High 8.8 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 7 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jpcp-6vj6-jf48

## What is CVE-2017-17435?

CVE-2017-17435 is a high-severity vulnerability in n/a, published on 7 Dec 2017. 

### Official description

An issue was discovered in the software on Vaultek Gun Safe VT20i products, aka BlueSteal. An attacker can remotely unlock any safe in this product line without a valid PIN code. Even though the phone application requires it and there is a field to supply the PIN code in an authorization request, the safe does not check the PIN code, so an attacker can obtain authorization using any value. Once an attacker sees the Bluetooth Low Energy (BLE) advertisement for the safe, they need only to write a BLE characteristic to enable notifications, and send a crafted getAuthor packet that returns a temporary key, and an unlock packet including that temporary key. The safe then opens after the unlock packet is processed, with no verification of PIN or other credentials.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2017-17435?

It affects 1 product.


Products: Vaulteksafe Vt20i Firmware.

## How do I fix CVE-2017-17435?

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

## Is CVE-2017-17435 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-17436](https://insights.sbomify.com/CVE-2017-17436/): Weak cryptography in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-17435 and fix it if it is affected.

What it is: CVE-2017-17435 is a high-severity vulnerability in n/a, published on 7 Dec 2017. 
Exploitation: There is no known exploitation of CVE-2017-17435 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-2017-17435/ (Markdown: https://insights.sbomify.com/CVE-2017-17435/index.md)
```

## Sources

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

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