# CVE-2023-29468: Memory corruption in n/a

> A buffer overflow in the TI WiLink WL18xx MCP driver allows remote code execution via crafted management frames.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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:** 14 Aug 2023
- **Updated:** 5 May 2025
- **Also known as:** GHSA-jp68-xw9h-gq7r

## What is CVE-2023-29468?

CVE-2023-29468 is a critical memory corruption vulnerability in n/a, published on 14 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Texas Instruments (TI) WiLink WL18xx MCP driver does not limit the number of information elements (IEs) of type XCC_EXT_1_IE_ID or XCC_EXT_2_IE_ID that can be parsed in a management frame. Using a specially crafted frame, a buffer overflow can be triggered that can potentially lead to remote code execution. This affects WILINK8-WIFI-MCP8 version 8.5_SP3 and earlier.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Ti Wilink8-Wifi-Mcp8.

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

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

## Is CVE-2023-29468 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-29468 is a critical memory corruption vulnerability in n/a, published on 14 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-29468 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-2023-29468/ (Markdown: https://insights.sbomify.com/CVE-2023-29468/index.md)
```

## Sources

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

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