| Título | 0x4m4 hexstrike-ai v1.0 Arbitrary File Write |
|---|
| Descripción | The HexStrike AI server exposes two file management endpoints — /api/files/create (POST) and /api/files/modify (POST) — that allow a client to create or modify files on the server's filesystem. The FileOperationsManager class uses Path("/tmp/hexstrike_files") / filename to construct the target path, but filename is entirely user-controlled and no path traversal protection is applied: no .resolve() check, no .. filtering, no chroot. An unauthenticated remote attacker can supply filename values containing ../ sequences to write to arbitrary locations on the filesystem, such as ~/.ssh/authorized_keys, ~/.bashrc, /etc/cron.d/, or any other file writable by the server process. This directly leads to persistent remote code execution. |
|---|
| Fuente | ⚠️ https://github.com/0x4m4/hexstrike-ai/issues/225 |
|---|
| Usuario | ez-lbz (UID 87033) |
|---|
| Sumisión | 2026-08-04 14:35 (hace 1 mes) |
|---|
| Moderación | 2026-09-13 07:08 (1 month later) |
|---|
| Estado | Aceptado |
|---|
| Entrada de VulDB | 403224 [0x4m4 HexStrike AI hasta d689933ff579d839c676c82b231f8e98326c5f04 API Files Endpoint hexstrike_server.py FileOperationsManager filename recorrido de directorios] |
|---|
| Puntos | 20 |
|---|