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

> A buffer overflow in the LBT-T300-T310 access point allows attackers to execute arbitrary code or cause a denial of service via the ApCliEncrypType parameter.

- **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:** 15 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-f6m7-x69c-hp72

## What is CVE-2023-50469?

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

### Official description

Shenzhen Libituo Technology Co., Ltd LBT-T300-T310 v2.2.2.6 was discovered to contain a buffer overflow via the ApCliEncrypType parameter at /apply.cgi.

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

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

It affects 1 product.


Products: Szlbt Lbt-T300-T310 Firmware.

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

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

## Is CVE-2023-50469 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-8019](https://insights.sbomify.com/CVE-2025-8019/): Shenzhen Libituo Technology LBT-T300-T310 appy.cgi sub_40B6F0 buffer overflow (high 8.7)
- [CVE-2025-7077](https://insights.sbomify.com/CVE-2025-7077/): Shenzhen Libituo Technology LBT-T300-T310 appy.cgi config_3g_para buffer overflow (high 8.7)
- [CVE-2023-47307](https://insights.sbomify.com/CVE-2023-47307/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-50469 is a critical memory corruption vulnerability in n/a, published on 15 Dec 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-50469 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-50469/ (Markdown: https://insights.sbomify.com/CVE-2023-50469/index.md)
```

## Sources

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

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