# CVE-2020-16630: Auth bypass in n/a

> Attackers can bypass Bluetooth authentication checks by spoofing MAC addresses, gaining unauthorized read and write access to protected device attributes.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/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:** 20 Sep 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-h5cr-94cg-hxmr

## What is CVE-2020-16630?

CVE-2020-16630 is a medium-severity authentication bypass vulnerability in n/a, published on 20 Sep 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

TI’s BLE stack caches and reuses the LTK’s property for a bonded mobile. A LTK can be an unauthenticated-and-no-MITM-protection key created by Just Works or an authenticated-and-MITM-protection key created by Passkey Entry, Numeric Comparison or OOB. Assume that a victim mobile uses secure pairing to pair with a victim BLE device based on TI chips and generate an authenticated-and-MITM-protection LTK. If a fake mobile with the victim mobile’s MAC address uses Just Works and pairs with the victim device, the generated LTK still has the property of authenticated-and-MITM-protection. Therefore, the fake mobile can access attributes with the authenticated read/write permission.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2020-16630?

It affects 7 products.


Products: Ti 15.4-Stack, Ti Ble5-Stack, Ti Dynamic Multi-Protocal Manager, Ti Easylink, Ti Openthread, Ti Real-Time Operating System, Ti Z-Stack.

## How do I fix CVE-2020-16630?

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

## Is CVE-2020-16630 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-16630 and fix it if it is affected.

What it is: CVE-2020-16630 is a medium-severity authentication bypass vulnerability in n/a, published on 20 Sep 2021. 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-2020-16630 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-2020-16630/ (Markdown: https://insights.sbomify.com/CVE-2020-16630/index.md)
```

## Sources

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

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