CVE-2025-70084
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDirectory traversal vulnerability in OpenSatKit 2.2.1 allows attackers to gain access to sensitive information or delete arbitrary files via crafted value to the FileUtil_GetFileInfo function.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceDirectory traversal vulnerability in OpenSatKit 2.2.1 in the FileUtil_GetFileInfo function allows attackers to use crafted path traversal sequences (e.g., '../') to access sensitive files outside the intended directory or delete arbitrary files on the system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.2.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify OpenSatKit installationLocate OpenSatKit installation directories or check system for opensatkit packages/components (common paths include /opt/opensatkit, /usr/local/opensatkit, or installation via package managers)Affected if OpenSatKit version 2.2.1 is found on the system
-
Verify OpenSatKit versionCheck the installed version of OpenSatKit using package manager queries, version flags (--version), or inspect version files within the installation directoryAffected if The installed version is exactly 2.2.1
-
Check for FileUtil_GetFileInfo usageSearch for code, scripts, or applications that call the FileUtil_GetFileInfo function within the OpenSatKit installation - review source code, binaries, or configuration files that reference this functionAffected if FileUtil_GetFileInfo is invoked by any application or script in the environment
-
Assess network exposureDetermine if the FileUtil_GetFileInfo function is accessible via network services, APIs, or web interfaces provided by OpenSatKitAffected if The function is exposed through network-accessible services without additional access controls
-
Test for path traversal accessIf FileUtil_GetFileInfo is accessible, attempt to use path traversal sequences (e.g., passing ../ paths as input) to verify if the vulnerability is exploitable in the current environmentAffected if The function accepts and processes path traversal sequences without rejecting them
A system is affected if OpenSatKit version 2.2.1 is installed and the FileUtil_GetFileInfo function is accessible and processes path traversal sequences without validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation and sanitization on the FileUtil_GetFileInfo function to reject path traversal sequences; enforce whitelisting of allowed paths and use canonicalization checks to ensure resolved paths remain within intended directories.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-70084 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-70084 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data