Skip to main content
VulnerabilityPublished Updated

CVE-2024-25395: rt-thread · Classic Buffer Overflow

Affects rt-threadSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 5.0.3 soon.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.0.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Mar 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Upgrade rt-thread/rt-thread to 5.0.3.

Affected software

ProductAffectedFixed in
GitHubrt-thread/rt-threadpkg:github/rt-thread/rt-threadOther threatsAffected
  • <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

To mitigate CVE-2024-25395, organizations should first identify all devices running RT-Thread up to version 5.0.2, particularly those exposed to network access. Since no official patches are currently available, immediate steps include restricting network access to vulnerable devices using firewalls and network segmentation to limit exposure. Implement strict input validation and memory safety checks in custom RT-Thread applications if source code access is available. Monitor network traffic for unusual activity that could indicate exploitation attempts. Engage with RT-Thread vendors or maintainers to obtain or request security patches and apply them promptly once released. Additionally, consider deploying intrusion detection systems (IDS) tailored for embedded environments to detect exploitation attempts. For long-term security, plan for firmware updates or device replacements that incorporate secure coding practices and hardened RTOS versions. Regular security audits of embedded and IoT devices should be conducted to identify and remediate similar vulnerabilities.

Description

A buffer overflow occurs in utilities/rt-link/src/rtlink.c in RT-Thread through 5.0.2.

References

Community reviews

Loading reviews…