# CVE-2023-45318: Memory corruption in Gecko Platform

> A heap-based buffer overflow in the uC-HTTP library allows remote attackers to execute arbitrary code via malicious network packets.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2024
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-j494-r8wx-qpjr

## What is CVE-2023-45318?

CVE-2023-45318 is a critical memory corruption vulnerability in Silicon Labs Gecko Platform, published on 20 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A heap-based buffer overflow vulnerability exists in the HTTP Server functionality of Weston Embedded uC-HTTP git commit 80d4004. A specially crafted network packet can lead to arbitrary code execution. An attacker can send a malicious packet to trigger this vulnerability.

Weakness: CWE-787 (Out-of-bounds Write), CWE-122 (Heap-based Buffer Overflow)

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

It affects 2 products.


Products: Silabs Gecko Software Development Kit, Weston-Embedded Uc-Http.

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

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

## Is CVE-2023-45318 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-45318 exists.

## Other vulnerabilities in Silicon Labs Gecko Platform

- [CVE-2023-2686](https://insights.sbomify.com/CVE-2023-2686/): Memory corruption in Gecko Platform (critical 9.8)
- [CVE-2023-4280](https://insights.sbomify.com/CVE-2023-4280/): Unvalidated input in Silicon Labs TrustZone implementation leads to accessing Trusted memory region (critical 9.3)
- [CVE-2023-4020](https://insights.sbomify.com/CVE-2023-4020/): Unvalidated input in Silicon Labs PSA Attestation service leads to secure memory access from non-secure memory (critical 9.0)
- [CVE-2023-25181](https://insights.sbomify.com/CVE-2023-25181/): Memory corruption in Cesium NET (critical 9.0)
- [CVE-2023-27882](https://insights.sbomify.com/CVE-2023-27882/): Memory corruption in Cesium NET (critical 9.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-45318 is a critical memory corruption vulnerability in Silicon Labs Gecko Platform, published on 20 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-45318 exists.

Affected product: Silicon Labs Gecko Platform. 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-45318/ (Markdown: https://insights.sbomify.com/CVE-2023-45318/index.md)
```

## Sources

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

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