# CVE-2020-12702: Weak cryptography in n/a

> Weak encryption in eWeLink app pairing allows nearby attackers to eavesdrop on Wi-Fi credentials and sensitive data.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 24 Feb 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4hq8-rhcf-fxwv

## What is CVE-2020-12702?

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

### Official description

Weak encryption in the Quick Pairing mode in the eWeLink mobile application (Android application V4.9.2 and earlier, iOS application V4.9.1 and earlier) allows physically proximate attackers to eavesdrop on Wi-Fi credentials and other sensitive information by monitoring the Wi-Fi spectrum during the pairing process.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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

It affects 1 product.


Products: Coolkit Ewelink.

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

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

## Is CVE-2020-12702 being exploited?

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

Public exploit code:

- eWeLinkESPT is a tool that automatically decodes and decrypts the WiFi network credentials transmitted to a supported ESP-based IoT device by the eWeLink mobile application. (CVE-2020-12702) (github_poc): https://github.com/salgio/ESPTouchCatcher
- This repo describes a vulnerability affecting the QR code based pairing process of the eWeLink IoT devices (CVE-2020-12702). (github_poc): https://github.com/salgio/eWeLink-QR-Code

## Other vulnerabilities in n/a

- [CVE-2023-6998](https://insights.sbomify.com/CVE-2023-6998/): Lockscreen bypass in eWeLink App (high 7.7)
- [CVE-2021-27941](https://insights.sbomify.com/CVE-2021-27941/): Information disclosure in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-12702 is a medium-severity vulnerability in n/a, published on 24 Feb 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-12702 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-12702/ (Markdown: https://insights.sbomify.com/CVE-2020-12702/index.md)
```

## Sources

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

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