CVE-2025-70083
Stack Buffer Overflow in OpenSatKit 2.2.1 Telecommand Path Handling
Publication date: 2026-02-11
Last updated on: 2026-02-17
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| opensatkit | opensatkit | 2.2.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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). |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in OpenSatKit 2.2.1 where the DirName field in a telecommand, which comes from the ground segment and is considered untrusted input, is copied into a local buffer using the unsafe function strcpy.
The local buffer, DirWithSep, has a fixed size defined by OS_MAX_PATH_LEN. If the length of DirName is equal to or exceeds this size, a stack buffer overflow occurs because the program copies the data before checking its length.
The validation to check the path length happens only after the copy operation, which is too late to prevent the overflow, potentially overwriting adjacent stack memory.
How can this vulnerability impact me? :
The stack buffer overflow caused by this vulnerability can lead to memory corruption, which may result in unpredictable behavior such as crashes or the execution of arbitrary code.
An attacker who controls the DirName input could exploit this to compromise the system's security, potentially gaining unauthorized access or causing denial of service.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know