Local memory corruption via unchecked DirName copy
Published Feb 11, 2026 · Updated Feb 11, 2026
Stack-based buffer overflow in OpenSatKit 2.2.1 allows local users to overwrite adjacent stack memory via a crafted DirName telecommand. The File Manager directory handlers call strcpy on the ground-supplied DirName before FileUtil_AppendPathSep checks OS_MAX_PATH_LEN. The flaw requires low-privileged access to submit ground-segment telecommands; successful exploitation corrupts control data or crashes the affected process.
Summary
What happened
Stack-based buffer overflow in OpenSatKit 2.2.1 allows local users to overwrite adjacent stack memory via a crafted DirName telecommand. The File Manager directory handlers call strcpy on the ground-supplied DirName before FileUtil_AppendPathSep checks OS_MAX_PATH_LEN. The flaw requires low-privileged access to submit ground-segment telecommands; successful exploitation corrupts control data or crashes the affected process.
The record
- CVE
- CVE-2025-70083
- Published
- Feb 11, 2026
- Updated
- Feb 11, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-121
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 11, 2026CVE publishedPublication date reported by the CVE source.
- Feb 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo