dbcve.org
Path TraversalWeakness · CWE-22

CVE-2024-35205

HIGH · 7.8 CVSS v3.1 Published 2024-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
The WPS Office (aka cn.wps.moffice_eng) application before 17.0.0 for Android fails to properly sanitize file names before processing them through external application interactions, leading to a form of path traversal. This potentially enables any application to dispatch a crafted library file, aiming to overwrite an existing native library utilized by WPS Office. Successful exploitation could result in the execution of arbitrary commands under the guise of WPS Office's application ID.

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 · high confidence

WPS Office Android app before v17.0.0 contains a path traversal vulnerability in its external application interaction handling. The app fails to sanitize file names before processing them, allowing a malicious application to dispatch a crafted library file to overwrite existing native libraries. Successful exploitation enables arbitrary command execution under WPS Office's application context.

MitigationUpgrade WPS Office to version 17.0.0 or later. Additionally, implement strict input validation and path sanitization for all file operations originating from external application interactions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WPS Office Android app is installed
    Run 'pm list packages | grep wps' or check installed apps via Settings > Apps for WPS Office
    Affected if WPS Office package is found on the device
  2. Check installed WPS Office version
    Run 'dumpsys package com.kingsoft.wpsoffice | grep versionName' or view version in app info screen
    Affected if Version is present and less than 17.0.0 (e.g., 16.x.x or earlier)
  3. Verify external application interaction is accessible
    Check if other apps can send Intents to WPS Office by examining app's exported components: 'dumpsys package com.kingsoft.wpsoffice | grep -i exported'
    Affected if Exported Activity, Service, or Receiver components are found that handle file-related intents
  4. Inspect native libraries for tampering
    Check /data/data/com.kingsoft.wpsoffice/lib/ or app's lib directory for unexpected .so files or modified timestamps compared to original APK lib contents
    Affected if Native libraries exist with unexpected names, sizes, or modification dates, or differ from those bundled in the original APK

If WPS Office Android version is below 17.0.0 and exported components handle external file intents, the device is affected by this path traversal vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade WPS Office to version 17.0.0 or later. Additionally, implement strict input validation and path sanitization for all file operations originating from external application interactions.

Recommended fix High confidence

WPS Office for Android version 17.0.0 or later

  1. Open the Google Play Store or your device's app store
  2. Search for "WPS Office" or "cn.wps.moffice_eng"
  3. Locate WPS Office in the search results
  4. If an update is available, tap "Update" to install version 17.0.0 or later
  5. Alternatively, uninstall the current version and reinstall WPS Office to ensure you have version 17.0.0 or newer
  6. Verify the installed version by checking the app's About or Settings section to confirm the version number is 17.0.0 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-35205 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-35205 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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