VulnerabilityPublished 27 Mar 2024Updated 4 Nov 2025

CVE-2024-25392: rt-thread · Out-of-bounds Read

Affects rt-threadSource CVE Database V5

Not known to be exploited · CVSS 5.9 Medium : upgrade to 5.0.3 when convenient.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

5.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 5.0.3

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Mar 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade rt-thread/rt-thread to 5.0.3.

Affected software

Product	Affected	Fixed in
GitHubrt-thread/rt-thread`pkg:github/rt-thread/rt-thread`Other threats	Affected <5.0.3	Fixed in 5.0.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Monitor RT-Thread vendor channels and security advisories closely for official patches addressing CVE-2024-25392 and apply them promptly once available. 2. Restrict local access to devices running RT-Thread to trusted personnel only, using strong physical and network access controls. 3. Implement network segmentation to isolate embedded devices and reduce the risk of lateral movement by attackers with local access. 4. Employ runtime memory protection mechanisms where possible, such as stack canaries or address space layout randomization (ASLR), if supported by the device. 5. Conduct thorough input validation and sanitization on data processed by var_export or related utilities to prevent malformed inputs triggering the OOB condition. 6. Use monitoring and anomaly detection tools to identify unusual device behavior indicative of exploitation attempts, such as crashes or memory errors. 7. For critical deployments, consider additional device hardening or temporary disabling of vulnerable components if feasible until patches are applied. 8. Educate local operators and administrators about the risks of local exploitation and enforce strict operational security policies.

Description

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

Impact

For European organizations, especially those deploying RT-Thread in embedded and IoT devices within industrial control systems, manufacturing, automotive, and smart infrastructure, this vulnerability poses a risk of localized denial of service or limited data integrity breaches. While the impact is not critical, exploitation could disrupt device functionality or cause data inconsistencies, affecting operational continuity. Given the prevalence of RT-Thread in industrial IoT, sectors such as manufacturing in Germany, automotive in France, and critical infrastructure in the UK could experience operational disturbances. The local attack vector limits remote exploitation but insider threats or compromised local networks could leverage this flaw. The medium severity indicates that while the vulnerability is not immediately catastrophic, it could be a stepping stone for more complex attacks if combined with other vulnerabilities. Organizations relying on embedded RT-Thread devices should consider the potential for downtime, data corruption, and the associated costs of incident response and recovery.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2025, 18:58 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats