Executive Summary

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.

Useful 0 Not Useful 0

Impact Analysis

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.

Useful 0 Not Useful 0

Mitigation Strategies

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.

Useful 0 Not Useful 0