# CVE-2020-13470: Information disclosure in n/a

> Physical attackers can extract sensitive data from Gigadevice microcontrollers by probing bonding wires and de-obfuscating the observed signals.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/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:** 31 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jw3x-c648-2hgq

## What is CVE-2020-13470?

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

### Official description

Gigadevice GD32F103 and GD32F130 devices allow physical attackers to extract data via the probing of easily accessible bonding wires and de-obfuscation of the observed data.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere)

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

It affects 2 products.


Products: Gigadevice Gd32f103 Firmware, Gigadevice Gd32f130 Firmware.

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

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

## Is CVE-2020-13470 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-13465](https://insights.sbomify.com/CVE-2020-13465/): Security feature bypass in n/a (medium 6.8)
- [CVE-2020-13472](https://insights.sbomify.com/CVE-2020-13472/): Security feature bypass in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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