# CVE-2024-25770: Denial of service in n/a

> A memory leak in libming allows attackers to cause denial of service by exhausting system memory.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **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:** 26 Feb 2024
- **Updated:** 9 Aug 2024
- **Also known as:** GHSA-5p7x-xg54-cjrq, UBUNTU-CVE-2024-25770

## What is CVE-2024-25770?

CVE-2024-25770 is a medium-severity denial of service vulnerability in Libming Libming, published on 26 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

libming 0.4.8 contains a memory leak vulnerability in /libming/src/actioncompiler/listaction.c.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

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

It affects 1 product.


Products: Libming Libming.

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

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

## Is CVE-2024-25770 being exploited?

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

## Other vulnerabilities in Libming Libming

- [CVE-2023-50628](https://insights.sbomify.com/CVE-2023-50628/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-11894](https://insights.sbomify.com/CVE-2020-11894/): Memory corruption in n/a (critical 9.1)
- [CVE-2020-11895](https://insights.sbomify.com/CVE-2020-11895/): Memory corruption in n/a (critical 9.1)
- [CVE-2019-16705](https://insights.sbomify.com/CVE-2019-16705/): Information disclosure in n/a (critical 9.1)
- [CVE-2023-36239](https://insights.sbomify.com/CVE-2023-36239/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-25770 is a medium-severity denial of service vulnerability in Libming Libming, published on 26 Feb 2024. 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-2024-25770 exists.

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

## Sources

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

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