Memory corruption via one-byte FUSE path overflow
Published Feb 20, 2024 · Updated Aug 2, 2024
Buffer overflow in Zephyr RTOS 3.5 and earlier allows local users to corrupt memory through a PATH_MAX-length FUSE path. The is_mount_point function copies the path with sprintf into a PATH_MAX-byte dir_path buffer, so the terminating null byte writes one byte past the buffer. The FUSE filesystem must be built and the local path operation reached; the overwrite corrupts adjacent memory and can crash the device.
Summary
What happened
Buffer overflow in Zephyr RTOS 3.5 and earlier allows local users to corrupt memory through a PATH_MAX-length FUSE path. The is_mount_point function copies the path with sprintf into a PATH_MAX-byte dir_path buffer, so the terminating null byte writes one byte past the buffer. The FUSE filesystem must be built and the local path operation reached; the overwrite corrupts adjacent memory and can crash the device.
The record
- CVE
- CVE-2023-6881
- Published
- Feb 20, 2024
- Updated
- Aug 2, 2024
- Vendor
- Zephyr Project
- Product
- Zephyr RTOS
- Classifications
- CWE-120, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 20, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record 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=* <=3.5
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