# CVE-2017-3215: Weak cryptography in ONE-KEY

> Attackers can hijack user accounts by exploiting long-lived bearer tokens in the Milwaukee ONE-KEY Android application.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vjpm-6m6x-4m32

## What is CVE-2017-3215?

CVE-2017-3215 is a medium-severity vulnerability in Milwaukee Tool ONE-KEY, published on 20 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Milwaukee ONE-KEY Android mobile application uses bearer tokens with an expiration of one year. This bearer token, in combination with a user_id can be used to perform user actions.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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

It affects 1 product.


Products: Milwaukee One-Key.

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

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

## Is CVE-2017-3215 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-3215 is a medium-severity vulnerability in Milwaukee Tool ONE-KEY, published on 20 Jun 2017. 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-2017-3215 in the wild and no public exploit code.

Affected product: Milwaukee Tool ONE-KEY. 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-3215/ (Markdown: https://insights.sbomify.com/CVE-2017-3215/index.md)
```

## Sources

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

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