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

> An out-of-bounds access in RT-Thread's var_export utility allows attackers to cause memory corruption, potentially leading to code execution or denial of service.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 27 Mar 2024
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-x7hf-f78p-hvvc

## What is CVE-2024-25392?

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

### Official description

An out-of-bounds access occurs in utilities/var_export/var_export.c in RT-Thread through 5.0.2.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Rt-Thread Rt-Thread.

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

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

## Is CVE-2024-25392 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-25393](https://insights.sbomify.com/CVE-2024-25393/): Memory corruption in n/a (critical 9.8)
- [CVE-2024-25395](https://insights.sbomify.com/CVE-2024-25395/): Memory corruption in n/a (high 8.8)
- [CVE-2025-5865](https://insights.sbomify.com/CVE-2025-5865/): RT-Thread Parameter lwp_syscall.c sys_select memory corruption (high 8.6)
- [CVE-2025-5866](https://insights.sbomify.com/CVE-2025-5866/): RT-Thread lwp_syscall.c sys_sigprocmask array index (high 8.6)
- [CVE-2025-5867](https://insights.sbomify.com/CVE-2025-5867/): RT-Thread lwp_syscall.c csys_sendto null pointer dereference (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-25392 is a medium-severity memory corruption vulnerability in n/a, published on 27 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-25392 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-25392/ (Markdown: https://insights.sbomify.com/CVE-2024-25392/index.md)
```

## Sources

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

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