GHSA-59xm-4m8c-g3xj: Path Traversal
Path Traversal via Unsanitized Identifier in Plugin Install/Uninstall
Summary The app-store plugin service concatenates unsanitized user-supplied identifier values directly into file system paths. An attacker can use path traversal sequences (e.g., ../) to read, install, or uninstall plugins from arbitrary directories, and potentially execute arbitrary composer commands.
Vulnerable Code
File: plugin/mine-admin/app-store/src/Service/Service.php
php // Line 32 - download(): path traversal via identifier public function download(array $params): bool { if (empty($params['identifier']) || empty($params['version'])) { $this->throwParamsFail(); } $service = make(AppStoreServiceImpl::class); if (! isdir(BASEPATH . '/plugin/' . $params['identifier'])) { // Path traversal $result = $service->download($params['identifier'], $params['version']); // ... } return true; }
// Line 48 - install(): path traversal + Plugin::install() with raw identifier public function install(array $params): bool { // ... $path = BASEPATH . '/plugin/' . $params['identifier']; // Path traversal if (fileexists($path . '/install.lock')) { $this->throwAppInstalled(); } Plugin::install($params['identifier']); // May run composer commands with traversal path return true; }
// Line 70 - unInstall(): same pattern public function unInstall(array $params): bool { // ... $path = BASEPATH . '/plugin/' . $params['identifier']; // Path traversal Plugin::uninstall($params['identifier']); // Arbitrary uninstall return true; }
File: plugin/mine-admin/app-store/src/Controller/IndexController.php (lines 25-26)
php #[Controller(prefix: 'admin/plugin/store')] #[Middleware(middleware: AccessTokenMiddleware::class, priority: 100)] // Only AccessTokenMiddleware -- no PermissionMiddleware (see GM-4340)
Proof of Concept
bash Install a "plugin" from a traversed path, potentially triggering composer on arbitrary directories curl -X POST "http://localhost:9501/admin/plugin/store/install" \ -H "Authorization: Bearer <JWTTOKEN>" \ -H "Content-Type: application/json" \ -d '{"identifier": "../app", "version": "1.0.0"}'
This resolves to BASEPATH/plugin/../app = BASEPATH/app Plugin::install("../app") processes the application directory as a plugin
Check if arbitrary path exists: curl -X POST "http://localhost:9501/admin/plugin/store/download" \ -H "Authorization: Bearer <JWTTOKEN>" \ -H "Content-Type: application/json" \ -d '{"identifier": "../../etc", "version": "1.0.0"}'
Impact
- Path traversal enables reading directory existence outside the plugin directory - Plugin::install() with a traversed identifier may run composer commands on arbitrary directories - Combined with GM-4340 (missing PermissionMiddleware), any authenticated user can exploit this - Could lead to arbitrary code execution depending on Plugin::install() implementation
Remediation
Validate and sanitize the identifier parameter to reject path traversal sequences. Use basename() or a strict regex allowlist (e.g., ^[a-zA-Z0-9-]+$) before concatenating into file paths.\n\n---\n\nUpdate: This finding has now been fully reproduced and validated in a Docker environment. The vulnerability is confirmed exploitable as described in the original report.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/mineadmin/mineadminto a version that resolves this vulnerability.Fixed in 3.2.0-alpha.2 - Configuration
In `plugin/mine-admin/app-store/src/Service/Service.php` (methods `download()`, `install()`, and `unInstall()`), validate and sanitize `identifier` from user input (`$params['identifier']`) to reject path traversal sequences before concatenating it into `$path` (BASE_PATH + '/plugin/' + identifier) or any derived filesystem path used by `Plugin::install()` / `Plugin::uninstall()`.
AppStore plugin service (plugin/mine-admin/app-store) Validate/sanitize `identifier` parameter before using it in filesystem paths = Reject path traversal sequences (e.g., `../`) and allow only a strict identifier format such as `^[a-zA-Z0-9_-]+$` (e.g., via `basename()` or regex allowlist)
Event History
Frequently Asked Questions
Who is realistically exposed to this issue?
Systems that expose app-store plugin download, install, or uninstall operations to attacker-controlled identifier values are affected. An attacker needs to supply a crafted identifier containing path-traversal sequences such as ../.
What actions could exploitation enable?
The vulnerable service uses the identifier directly when constructing paths under the plugin directory, including during download and install handling. This can allow access to arbitrary directories and may enable arbitrary composer command execution.
What can be done if patching is not immediately possible?
The provided data does not identify a workaround. Until an update is applied, restrict access to plugin-management operations and ensure untrusted users cannot control plugin identifier values.
How can I look for signs of attempted exploitation?
Review requests and application logs for plugin identifier values containing traversal patterns such as ../, especially around download, install, and uninstall operations. The affected code constructs plugin paths directly from this value.