# CVE-2023-3487: Integer overflow in Silicon Labs Gecko Bootloader leads to unbounded memory access

> An integer overflow in Silicon Labs Gecko Bootloader allows unbounded memory access, potentially enabling code execution or data disclosure.

- **Severity:** High 7.7 (`CVSS:3.1/AV:L/AC:L/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 Oct 2023
- **Updated:** 25 Sep 2024
- **Also known as:** GHSA-vx25-5r7c-m73f

## What is CVE-2023-3487?

CVE-2023-3487 is a high-severity vulnerability in silabs.com GSDK, published on 20 Oct 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An integer overflow in Silicon Labs Gecko Bootloader version 4.3.1 and earlier allows unbounded memory access when reading from or writing to storage slots.

Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-787 (Out-of-bounds Write), CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2023-3487?

It affects 1 product.


Products: Silabs Gecko Bootloader.

## How do I fix CVE-2023-3487?

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

## Is CVE-2023-3487 being exploited?

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

## Other vulnerabilities in silabs.com GSDK

- [CVE-2023-4041](https://insights.sbomify.com/CVE-2023-4041/): Second Stage Gecko Bootloader GBL Parser Buffer Overrun Vulnerability (critical 9.8)
- [CVE-2022-24936](https://insights.sbomify.com/CVE-2022-24936/): Gecko Standalone Bootloader vulnerability may allow bypassing application secure boot in some Series 2 devices (high 8.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-3487 and fix it if it is affected.

What it is: CVE-2023-3487 is a high-severity vulnerability in silabs.com GSDK, published on 20 Oct 2023. 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-2023-3487 in the wild and no public exploit code.

Affected product: silabs.com GSDK. 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-2023-3487/ (Markdown: https://insights.sbomify.com/CVE-2023-3487/index.md)
```

## Sources

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

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