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

> Attackers can cause a Denial of Service on LBT T300-T390 devices via a crafted POST request exploiting a stack overflow.

- **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:** 1 Mar 2024
- **Updated:** 22 Aug 2024
- **Also known as:** GHSA-5q6f-gm4w-g552

## What is CVE-2024-27571?

CVE-2024-27571 is a high-severity memory corruption vulnerability in n/a, published on 1 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LBT T300-T390 v2.2.1.8 were discovered to contain a stack overflow via the ApCliSsid parameter in the makeCurRemoteApList function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted POST request.

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

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

It affects 1 product.


Products: Libtor Lbt-T300-T390 Firmware.

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

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

## Is CVE-2024-27571 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-27570](https://insights.sbomify.com/CVE-2024-27570/): Memory corruption in n/a (high 7.5)
- [CVE-2024-27572](https://insights.sbomify.com/CVE-2024-27572/): Memory corruption in n/a (high 7.5)
- [CVE-2024-27567](https://insights.sbomify.com/CVE-2024-27567/): Memory corruption in n/a (medium 6.5)
- [CVE-2024-27568](https://insights.sbomify.com/CVE-2024-27568/): Memory corruption in n/a (medium 6.5)
- [CVE-2024-27569](https://insights.sbomify.com/CVE-2024-27569/): Memory corruption in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-27571 is a high-severity memory corruption vulnerability in n/a, published on 1 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-27571 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-27571/ (Markdown: https://insights.sbomify.com/CVE-2024-27571/index.md)
```

## Sources

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

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