# CVE-2020-11015: Device Authentication Vulnerability in thinx-device-api IoT Device Management Server

> Attackers can spoof MAC addresses to bypass device authentication and register unauthorized devices in the thinx IoT management system.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/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:** 29 Sep 2022
- **Updated:** 23 Apr 2025

## What is CVE-2020-11015?

CVE-2020-11015 is a high-severity authentication bypass vulnerability in suculent thinx-device-api, published on 29 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been disclosed in thinx-device-api IoT Device Management Server before version 2.5.0. Device MAC address can be spoofed. This means initial registration requests without UDID and spoofed MAC address may pass to create new UDID with same MAC address. Full impact needs to be reviewed further. Applies to all (mostly ESP8266/ESP32) users. This has been fixed in firmware version 2.5.0.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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

It affects 1 product.


Products: Thinx-Device-Api Project Thinx-Device-Api.

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

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

## Is CVE-2020-11015 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11015 is a high-severity authentication bypass vulnerability in suculent thinx-device-api, published on 29 Sep 2022. 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-2020-11015 in the wild and no public exploit code.

Affected product: suculent thinx-device-api. 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-11015/ (Markdown: https://insights.sbomify.com/CVE-2020-11015/index.md)
```

## Sources

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

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