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

> Attackers can cause a denial of service on Libituo wireless access points via a buffer overflow in the apply.cgi endpoint.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 30 Nov 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-2vv4-6qfr-v4vp

## What is CVE-2023-47307?

CVE-2023-47307 is a high-severity memory corruption vulnerability in n/a, published on 30 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer Overflow vulnerability in /apply.cgi in Shenzhen Libituo Technology Co., Ltd LBT-T300-T310 v2.2.2.6 allows attackers to cause a denial of service via the ApCliAuthMode parameter.

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

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

It affects 1 product.


Products: Szlbt Lbt-T300-T310 Firmware.

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

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

## Is CVE-2023-47307 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-50469](https://insights.sbomify.com/CVE-2023-50469/): Memory corruption in n/a (critical 9.8)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-47307 is a high-severity memory corruption vulnerability in n/a, published on 30 Nov 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-47307 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-47307/ (Markdown: https://insights.sbomify.com/CVE-2023-47307/index.md)
```

## Sources

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

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