Memory corruption via unchecked ROMFS name copy
Published Mar 27, 2024 · Updated Nov 4, 2025
Heap buffer overflow in RT-Thread 5.0.2 and earlier allows local users to corrupt memory by listing a crafted dfs_v2 ROMFS directory. dfs_romfs_getdents passes rt_strlen(name) + 1 to rt_strncpy without limiting the copy to d_name, so an overlong entry name overwrites heap memory. Triggering requires DFS v2 with ROMFS enabled and an overlong directory entry; the published analysis does not establish a reliable post-corruption outcome.
Summary
What happened
Heap buffer overflow in RT-Thread 5.0.2 and earlier allows local users to corrupt memory by listing a crafted dfs_v2 ROMFS directory. dfs_romfs_getdents passes rt_strlen(name) + 1 to rt_strncpy without limiting the copy to d_name, so an overlong entry name overwrites heap memory. Triggering requires DFS v2 with ROMFS enabled and an overlong directory entry; the published analysis does not establish a reliable post-corruption outcome.
The record
- CVE
- CVE-2024-24335
- Published
- Mar 27, 2024
- Updated
- Nov 4, 2025
- Vendor
- RT-Thread
- Product
- RT-Thread
- Classifications
- CWE-122
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 27, 2024CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=5.0.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo