# CVE-2024-28447: Memory corruption in n/a

> A buffer overflow in the LBT-T300-mini1 device allows attackers to execute arbitrary code or cause denial of service via crafted parameters.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Mar 2024
- **Updated:** 20 Aug 2024
- **Also known as:** GHSA-8gwm-v64w-x477

## What is CVE-2024-28447?

CVE-2024-28447 is a medium-severity memory corruption vulnerability in n/a, published on 19 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Shenzhen Libituo Technology Co., Ltd LBT-T300-mini1 v1.2.9 was discovered to contain a buffer overflow via lan_ipaddr parameters at /apply.cgi.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2024-28447?

It affects 1 product.


Products: Szlbt Lbt-T300-Mini1 Firmware.

## How do I fix CVE-2024-28447?

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

## Is CVE-2024-28447 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-29243](https://insights.sbomify.com/CVE-2024-29243/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-28446](https://insights.sbomify.com/CVE-2024-28446/): Memory corruption in n/a (medium 5.7)
- [CVE-2024-29244](https://insights.sbomify.com/CVE-2024-29244/): Memory corruption in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-28447 and fix it if it is affected.

What it is: CVE-2024-28447 is a medium-severity memory corruption vulnerability in n/a, published on 19 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-28447 exists.

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-2024-28447/ (Markdown: https://insights.sbomify.com/CVE-2024-28447/index.md)
```

## Sources

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

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