OpenSatKit 2.2.1 file.c FILE_ConcatenateCmd stack-based overflow

Summaryinfo

A vulnerability marked as critical has been reported in OpenSatKit 2.2.1. Affected by this vulnerability is the function FILE_ConcatenateCmd of the file file.c. The manipulation leads to stack-based overflow. This vulnerability is uniquely identified as CVE-2025-70085. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in OpenSatKit 2.2.1 and classified as critical. This issue affects the function FILE_ConcatenateCmd of the file file.c. The manipulation with an unknown input leads to a stack-based overflow vulnerability. Using CWE to declare the problem leads to CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). Impacted is confidentiality, integrity, and availability. The summary by CVE is:

An issue was discovered in OpenSatKit 2.2.1. The EventErrStr buffer has a fixed size of 256 bytes. The code uses sprintf to format two filenames (Source1Filename and the string returned by FileUtil_FileStateStr) into this buffer without any length checking and without using bounded format specifiers such as %.*s. If the filename length approaches OS_MAX_PATH_LEN (commonly 64-256 bytes), the combined formatted string together with constant text can exceed 256 bytes, resulting in a stack buffer overflow. Such unsafe sprintf calls are scattered across multiple functions in file.c, including FILE_ConcatenateCmd() and ConcatenateFiles(), all of which fail to validate the output length.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2025-70085 since 01/09/2026. The exploitation is known to be easy. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 2.2.1 eliminates this vulnerability. The upgrade is hosted for download at github.com.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• OpenSatKit

Version

• 2.2.1

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion