You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There was a serious bug in older versions of the trim-cache script that could delete arbitrary files by accident. To trigger it, you had to install TIO at least partially. If you just cloned the repo, you're safe.
Note that triggering the bug requiring executing commands on a machine you control. It's not possible to trigger it from the sandbox.
Realistically, I think it could only be triggered in two scenarios. Do NOT perform these steps.
In a manual install, the following would trigger the bug.
Clone the tryitonline repo to /srv (that exact path).
Create a valid trim-cache configuration file in /srv/etc.
Fail to create a /srv/cache directory.
Run the trim-cache script in a directory where you have write access to sub-directories, either manually or via the systemd unit files in the tryitonline repo.
With tiosetup, the following would trigger the bug.
Perform a full install or at least run the scripts in the stage directory.
Delete the /srv/cache directory.
Leave the tio-web service running or start/install the tio-trim-cache service/timer manually.
In this case, the trim-cache script would be run as root in /, deleting most system files.
As of commit b1967d1, aside from fixing the faulty script, the systemd unit file now runs it with write access to /srv/cache and nothing else.
If you know anyone who might be running a TIO server, please point them to this issue.
The text was updated successfully, but these errors were encountered:
There was a serious bug in older versions of the trim-cache script that could delete arbitrary files by accident. To trigger it, you had to install TIO at least partially. If you just cloned the repo, you're safe.
Note that triggering the bug requiring executing commands on a machine you control. It's not possible to trigger it from the sandbox.
Realistically, I think it could only be triggered in two scenarios. Do NOT perform these steps.
In a manual install, the following would trigger the bug.
/srv
(that exact path).trim-cache
configuration file in/srv/etc
./srv/cache
directory.trim-cache
script in a directory where you have write access to sub-directories, either manually or via the systemd unit files in the tryitonline repo.With tiosetup, the following would trigger the bug.
/srv/cache
directory.In this case, the
trim-cache
script would be run as root in/
, deleting most system files.As of commit b1967d1, aside from fixing the faulty script, the systemd unit file now runs it with write access to
/srv/cache
and nothing else.If you know anyone who might be running a TIO server, please point them to this issue.
The text was updated successfully, but these errors were encountered: