Memory corruption via overflowing log size check
Published Nov 8, 2022 · Updated Apr 22, 2025
Buffer overflow in Eclipse ThreadX FileX before 6.2.0 allows attackers to modify memory through a crafted fault-tolerant directory log. The _fx_fault_tolerant_apply_logs function adds attacker-controlled copy offsets and lengths in native-width arithmetic, allowing the bounds calculation to wrap before a buffer copy. Exploitation requires the Fault Tolerant feature to accept a log with a valid identifier and checksum; the bounded reported consequence is memory-content modification.
Summary
What happened
Buffer overflow in Eclipse ThreadX FileX before 6.2.0 allows attackers to modify memory through a crafted fault-tolerant directory log. The _fx_fault_tolerant_apply_logs function adds attacker-controlled copy offsets and lengths in native-width arithmetic, allowing the bounds calculation to wrap before a buffer copy. Exploitation requires the Fault Tolerant feature to accept a log with a valid identifier and checksum; the bounded reported consequence is memory-content modification.
The record
- CVE
- CVE-2022-39343
- Published
- Nov 8, 2022
- Updated
- Apr 22, 2025
- Vendor
- The Eclipse Foundation
- Product
- Eclipse ThreadX FileX
- Classifications
- CWE-191, CWE-190, CWE-120
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 8, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 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=< 6.2.0
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
- GitHub crafted fault-tolerant directory-log demonstrationproof of concept · demonstrated
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