Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-25393: n/a

0
Critical
VulnerabilityCVE-2024-25393cvecve-2024-25393
Published: Wed Mar 27 2024 (03/27/2024, 00:00:00 UTC)
Source: CVE Database V5

Description

A stack buffer overflow occurs in net/at/src/at_server.c in RT-Thread through 5.0.2.

AI-Powered Analysis

AILast updated: 11/04/2025, 18:58:16 UTC

Technical Analysis

CVE-2024-25393 is a stack-based buffer overflow vulnerability identified in the net/at/src/at_server.c source file of the RT-Thread real-time operating system, affecting versions through 5.0.2. RT-Thread is widely used in embedded systems and IoT devices, providing real-time capabilities for industrial, consumer, and automotive applications. The vulnerability arises from improper bounds checking in the AT command server component, which processes network input. An attacker with network access can send specially crafted packets to overflow the stack buffer, leading to arbitrary code execution. This flaw requires no privileges or user interaction, making it highly exploitable remotely. The vulnerability is classified under CWE-121 (Stack-based Buffer Overflow), which typically allows attackers to overwrite return addresses or control data on the stack, resulting in full system compromise. The CVSS v3.1 score of 9.8 reflects the critical impact on confidentiality, integrity, and availability, combined with low attack complexity and no required privileges. Although no public exploits have been reported yet, the vulnerability's nature and the widespread use of RT-Thread in critical embedded environments make it a significant threat. Currently, no official patches are linked, so affected organizations must monitor vendor advisories closely. The vulnerability's exploitation could disrupt industrial control systems, smart devices, and other embedded applications relying on RT-Thread, potentially causing operational downtime, data breaches, or device takeover.

Potential Impact

For European organizations, the impact of CVE-2024-25393 is substantial, especially those relying on RT-Thread-based embedded systems in critical infrastructure, manufacturing, automotive, and IoT sectors. Exploitation could lead to complete device compromise, allowing attackers to manipulate device behavior, exfiltrate sensitive data, or disrupt services. This is particularly concerning for industrial control systems and smart manufacturing environments prevalent in countries like Germany, France, and Italy, where RT-Thread may be embedded in automation equipment. The vulnerability could also affect consumer IoT devices, impacting privacy and security for end-users. Given the critical severity and remote exploitability, attackers could leverage this flaw to establish persistent footholds within networks, escalate attacks, or cause widespread operational disruptions. The absence of known exploits currently provides a window for proactive defense, but the risk of rapid weaponization remains high. The potential for cascading effects on supply chains and critical services elevates the threat level across the European Union and associated countries.

Mitigation Recommendations

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.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2024-02-07T00:00:00.000Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 690a475f6d939959c8022db3

Added to database: 11/4/2025, 6:35:11 PM

Last enriched: 11/4/2025, 6:58:16 PM

Last updated: 11/5/2025, 12:40:36 PM

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats