Security Resilience

CVE-2025-70085

Memory Safety in Opensatkit 2.2.1

Memory Safety
Published
11 February 2026
Modified
17 February 2026
Patch / advisory
View advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0062 49th percentile
Risk Priority 72 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-70085 is a critical-severity Stack-based Buffer Overflow (CWE-121) vulnerability in Opensatkit Opensatkit. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Compromise Infrastructure (T1584); ranked at the 49th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-70085, published on 2026-02-11, is a stack buffer overflow vulnerability (CWE-121) in OpenSatKit version 2.2.1. The flaw resides in the file manager component at cfs/apps/filemgr/fsw/src/file.c, where the EventErrStr buffer is fixed at 256 bytes. Code in multiple functions, including FILE_ConcatenateCmd() and ConcatenateFiles(), uses sprintf to format two filenames—Source1Filename and the string from FileUtil_FileStateStr—without length validation or bounded specifiers like %.*s. Filenames approaching OS_MAX_PATH_LEN (typically 64-256 bytes), combined with constant text, exceed the buffer size, triggering the overflow.

The vulnerability carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating network-accessible exploitation with low attack complexity, no privileges, no user interaction, and unchanged scope. Remote attackers can trigger the buffer overflow, potentially achieving high-impact compromise of confidentiality, integrity, and availability, such as arbitrary code execution on affected systems running the vulnerable OpenSatKit instance.

References provided include a GitHub Gist (https://gist.github.com/jonafk555) likely detailing the discovery, the OpenSatKit repository (https://github.com/OpenSatKit/OpenSatKit), the v2.2.1 release page (https://github.com/OpenSatKit/OpenSatKit/releases/tag/v2.2.1), and the vulnerable source file (https://raw.githubusercontent.com/OpenSatKit/OpenSatKit/master/cfs/apps/filemgr/fsw/src/file.c). No explicit patch or mitigation guidance is detailed in the CVE description.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-121

Related Threats

MITRE ATT&CK Enterprise Techniques

T1584 Compromise Infrastructure Resource Development
Adversaries may compromise third-party infrastructure that can be used during targeting.
attack.mitre.org →
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-70083Same product: Opensatkit Opensatkit
CVE-2025-70084Same product: Opensatkit Opensatkit
CVE-2026-24465Shared CWE-121
CVE-2025-70242Shared CWE-121
CVE-2026-15722Shared CWE-121
CVE-2026-76861Shared CWE-121
CVE-2026-66086Shared CWE-121
CVE-2024-2810Shared CWE-121
CVE-2026-112257Shared CWE-121
CVE-2024-45162Shared CWE-121

Affected Assets

opensatkit
opensatkit
2.2.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 2 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and analysis can discover stack-buffer overflows before deployment.

SI-10 Information Input Validation good match

Input validation directly stops untrusted data from exceeding stack buffer bounds.

SI-16 Memory Protection good match

Memory-protection mechanisms limit the ability to execute injected code after a stack overflow.

SA-8 Security and Privacy Engineering Principles partial match

Secure-engineering principles include bounds-checked coding and safe buffer handling that avoid introducing the flaw.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
blocks

Secure-development practices directly prevent introduction of stack buffer overflows.

ID.RA-01 partial match
blocks

Vulnerability scanning can discover stack buffer overflows but does not prevent their introduction.

PR.PS-02 partial match
blocks

Patching eliminates known instances of the weakness after discovery.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing (fuzzing, static analysis) detects stack overflows before release.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe buffer handling that causes CWE-121.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248594 OL 8 must implement address space layout randomization (ASLR) to protect its memory from unauthorized code execution. blocks CWE-121
Oracle Linux 9 (1 rule)
  • V-271452 OL 9 must use a Linux Security Module configured to enforce limits on system services. blocks CWE-121

References