CVE-2026-41144
Integer Overflow in F´ Framework File Handling Enables Arbitrary Write
Publication date: 2026-04-22
Last updated on: 2026-04-22
Assigner: Wed, 22 Apr 2026
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| nasa | fprime | From 0 (inc) to 4.2.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
| CWE-190 | The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the F´ (F Prime) framework prior to version 4.2.0. It involves a logic bug in the bounds check for file writes, where the addition of byteOffset and dataSize uses 32-bit unsigned integer addition that wraps around on overflow. An attacker can craft a DataPacket with specific values (byteOffset=0xFFFFFF9C and dataSize=100) that causes the addition to overflow to zero, bypassing the bounds check entirely.
Additionally, the code does not sanitize the destination file path, allowing an attacker to write arbitrary data to any file at any offset. This can lead to arbitrary file writes and potentially remote code execution on embedded targets using the framework.
This is a logic bug affecting file I/O operations, and typical memory error detection tools like ASAN do not detect it because all memory accesses remain within valid buffers.
How can this vulnerability impact me? :
The vulnerability allows an attacker to write arbitrary data to any file at any offset on embedded targets using the affected F Prime framework versions. This can lead to arbitrary file writes and potentially remote code execution.
Such an exploit could compromise the integrity and security of the embedded system, potentially allowing attackers to execute malicious code remotely, disrupt system operations, or manipulate critical files.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is fixed in F Prime version 4.2.0. Immediate mitigation involves upgrading to version 4.2.0 or later.
No known workarounds are available.