# CVE-2024-7206: Firmware extraction and Hardware SSL Pinning Bypass

> Local attackers can bypass SSL pinning and extract secrets from modified firmware to decrypt TLS traffic and clone the device.

- **Severity:** High 7.0 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA: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:** 8 Oct 2024
- **Updated:** 8 Oct 2024
- **Also known as:** GHSA-rx6q-6v39-c6q2

## What is CVE-2024-7206?

CVE-2024-7206 is a high-severity vulnerability in eWeLink Zigbee Bridge Pro, published on 8 Oct 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SSL Pinning Bypass in eWeLink Some hardware products allows local ATTACKER to Decrypt TLS communication and Extract secrets to clone the device via Flash the modified firmware

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2024-7206?


## How do I fix CVE-2024-7206?

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

## Is CVE-2024-7206 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-7206 and fix it if it is affected.

What it is: CVE-2024-7206 is a high-severity vulnerability in eWeLink Zigbee Bridge Pro, published on 8 Oct 2024. 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-2024-7206 in the wild and no public exploit code.

Affected product: eWeLink Zigbee Bridge Pro. 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-2024-7206/ (Markdown: https://insights.sbomify.com/CVE-2024-7206/index.md)
```

## Sources

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

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