Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2025-70083 is a high-severity Stack-based Buffer Overflow (CWE-121) vulnerability in Opensatkit Opensatkit. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Compromise Infrastructure (T1584); ranked at the 12th 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-70083 is a stack buffer overflow vulnerability (CWE-121) affecting OpenSatKit version 2.2.1. The flaw exists in the file manager component at cfs/apps/filemgr/fsw/src/dir.c, where the DirName field from a telecommand—provided by the ground segment and treated as untrusted input—is copied into the local buffer DirWithSep using strcpy. This buffer is limited to OS_MAX_PATH_LEN bytes, but if DirName is greater than or equal to this length, the copy overflows adjacent stack memory. A subsequent path length check with FileUtil_AppendPathSep occurs after the strcpy, rendering it ineffective for prevention.
The vulnerability carries a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Exploitation requires local access and low privileges, allowing an attacker to send a telecommand with an overly long DirName. Successful exploitation can result in high-impact consequences, including unauthorized data access, modification, or destruction (confidentiality and integrity), as well as system crashes or disruption (availability), potentially leading to arbitrary code execution via stack overwrite.
References provided include the OpenSatKit GitHub repository, the v2.2.1 release tag, a GitHub Gist, and raw source code excerpts pinpointing the vulnerable strcpy operation. Practitioners should consult these, particularly the repository, for any available patches, updated releases, or mitigation guidance beyond version 2.2.1.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-207394
Vulnerability Data
An issue was discovered in OpenSatKit 2.2.1. The DirName field in the telecommand is provided by the ground segment and must be treated as untrusted input. The program copies DirName into the local buffer DirWithSep using strcpy. The size of…
more
this buffer is OS_MAX_PATH_LEN. If the length of DirName is greater than or equal to OS_MAX_PATH_LEN, a stack buffer overflow occurs, overwriting adjacent stack memory. The path length check (FileUtil_AppendPathSep) is performed after the strcpy operation, meaning the validation occurs too late and cannot prevent the overflow.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 2 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and analysis can discover stack-buffer overflows before deployment.
Input validation directly stops untrusted data from exceeding stack buffer bounds.
Memory-protection mechanisms limit the ability to execute injected code after a stack overflow.
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.
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.
Security testing (fuzzing, static analysis) detects stack overflows before release.
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