# CVE-2025-7077: Shenzhen Libituo Technology LBT-T300-T310 appy.cgi config_3g_para buffer overflow

> Remote attackers can trigger a buffer overflow in the LBT-T300-T310 web interface via crafted parameters, potentially executing arbitrary code.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jul 2025
- **Updated:** 7 Jul 2025
- **Also known as:** GHSA-mg9j-87r8-p39p

## What is CVE-2025-7077?

CVE-2025-7077 is a high-severity memory corruption vulnerability in Shenzhen Libituo Technology LBT-T300-T310, published on 6 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability classified as critical has been found in Shenzhen Libituo Technology LBT-T300-T310 up to 2.2.3.6. This affects the function config_3g_para of the file /appy.cgi. The manipulation of the argument username_3g/password_3g leads to buffer overflow. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. Other parameters might be affected as well. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2025-7077?

It affects 1 product.


Products: Szlbt Lbt-T300-T310 Firmware.

## How do I fix CVE-2025-7077?

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

## Is CVE-2025-7077 being exploited?

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

## Other vulnerabilities in Shenzhen Libituo Technology LBT-T300-T310

- [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-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-2025-7077 and fix it if it is affected.

What it is: CVE-2025-7077 is a high-severity memory corruption vulnerability in Shenzhen Libituo Technology LBT-T300-T310, published on 6 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-7077 exists.

Affected product: Shenzhen Libituo Technology LBT-T300-T310. 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-2025-7077/ (Markdown: https://insights.sbomify.com/CVE-2025-7077/index.md)
```

## Sources

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

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