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
{{ message }}
This repository has been archived by the owner on Jan 26, 2022. It is now read-only.
It is really dangerous to execute a world writable file with root privileges. Anyone with storage access could add their own and possibly malicious commands to that file and use root permissions in the name of ts-binds. To prevent this, the config file must either be protected or never executed on a shell. Parsing the file directly inside ts-binds could do the trick here.
The text was updated successfully, but these errors were encountered:
Hello. Thank you so much for reporting this! When the project was small and personal, I used the sourcing method as an easy way to use a makeshift configuration method. I was aware that this is a huge vulnerability but I figured it wouldn't be a problem since the project was really, really small. Alas, I have forgotten about it.
Thanks to you, I am reminded about it again. Certainly, I will look for ways to read from a file safely instead of executing/sourcing it. But first I need to solve a number of bugs reported on XDA thread. I hope that would not bother you.
It is really dangerous to execute a world writable file with root privileges. Anyone with storage access could add their own and possibly malicious commands to that file and use root permissions in the name of ts-binds. To prevent this, the config file must either be protected or never executed on a shell. Parsing the file directly inside ts-binds could do the trick here.
The text was updated successfully, but these errors were encountered: