CVE-2024-25393: rt-thread · n/a
Affects rt-threadSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 5.0.3 as a priority.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 64% 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:N/UI:N/S:U/C:H/I:H/A:HExploitation 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 2026-10-25.
What to do
Upgrade rt-thread/rt-thread to 5.0.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubrt-thread/rt-threadpkg:github/rt-thread/rt-threadOther threats | Affected
| Fixed in
|
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 for official patches addressing CVE-2024-25393 and apply them immediately upon release. 2. In the interim, restrict network access to devices running RT-Thread, especially limiting exposure of the AT command server component to untrusted networks. 3. Employ network segmentation and firewall rules to isolate vulnerable embedded devices from critical infrastructure and sensitive networks. 4. Implement intrusion detection and prevention systems (IDS/IPS) with signatures or anomaly detection capable of identifying malformed AT command packets or unusual traffic patterns targeting the at_server component. 5. Conduct thorough inventory and asset management to identify all RT-Thread deployments within the organization, including embedded and IoT devices. 6. Where possible, disable or limit the functionality of the AT command server if not required for device operation. 7. Engage with device manufacturers to confirm patch availability and timelines, and request security updates if none are forthcoming. 8. Prepare incident response plans tailored to embedded device compromise scenarios to enable rapid containment and recovery.
Description
A stack buffer overflow occurs in net/at/src/at_server.c in RT-Thread through 5.0.2.
References
- github.com/RT-Thread/rt-thread/issues/8288 (opens in a new tab)
- github.com/hnsecurity/vulns/blob/main/HNS-2024-05-rt-thread.txt (opens in a new tab)
- security.humanativaspa.it/multiple-vulnerabilities-in-rt-thread-rtos/ (opens in a new tab)
- seclists.org/fulldisclosure/2024/Mar/28 (opens in a new tab)
- openwall.com/lists/oss-security/2024/03/05/1 (opens in a new tab)
- seclists.org/fulldisclosure/2024/Mar/28 (opens in a new tab)