Stack corruption via off-by-one FUSE path write
Published Sep 26, 2023 · Updated Feb 13, 2025
Buffer overflow in the FUSE filesystem layer in Zephyr RTOS 3.4.0 and earlier allows local users to corrupt stack memory. The fuse_fs_access_readdir function appends a slash with sprintf to a PATH_MAX-sized path in a PATH_MAX stack buffer, writing the terminating NUL one byte past mount_path. The path must reach a FUSE mount-point directory from a low-privileged local context; the resulting corruption can crash the process or execute code across the security boundary.
Summary
What happened
Buffer overflow in the FUSE filesystem layer in Zephyr RTOS 3.4.0 and earlier allows local users to corrupt stack memory. The fuse_fs_access_readdir function appends a slash with sprintf to a PATH_MAX-sized path in a PATH_MAX stack buffer, writing the terminating NUL one byte past mount_path. The path must reach a FUSE mount-point directory from a low-privileged local context; the resulting corruption can crash the process or execute code across the security boundary.
The record
- CVE
- CVE-2023-4260
- Published
- Sep 26, 2023
- Updated
- Feb 13, 2025
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-120, CWE-193
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 26, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 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 <=3.4
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