mirror of
https://github.com/Studio-Saelix/sencho.git
synced 2026-08-05 08:27:42 +00:00
73f4bc27c3
The file-explorer root containment treated only kernel and OS-state paths (/etc, /proc, /sys, /dev, /run, /var/run) as dangerous. System locations that hold the executables and libraries Sencho's own runtime depends on, notably /usr (which contains /usr/local/bin/node, the docker CLI, and the entrypoint) plus /bin, /sbin, /lib, /lib64, /boot and /root, were left browsable, writable and chmodable. A stack author with stack:edit could declare one of these as a bind source, overwrite a binary, and have a later deploy execute it. Add those locations to the dangerous-root set so such a bind is never browsable or editable; the boundary check still permits ordinary host paths whose name merely prefixes a protected root (for example /usrdata).