Security Issues
Status: Inactive
Brought to you by:
smi13y
Menu
▾
▴
#1 Security Issues
TimeSaver has two features that could potentially be
security hazards: the dialog that asks for the command
to the web browser in which you wish to visit the
TimeSaver home page, and the loading of .xml files for
reports on a given session. In the former case, I have
proved that any person with physical access to the
terminal on which TimeSaver is running may be able to
do harm to the system (e.g., delete important files,
etc) by simply entering another command instead of a
command that would launch a web browser (e.g., rm
./importantfile or kdesu 'konsole -e mkfs.ext3
/dev/hdx). To rectify this issue, I reccomend an
implementation of a feature of that any command other
than a command to launch a web browser executeable (or
an execuetable not in /usr/bin, /bin or another path
where the shell would look for executables) be
rejected, instead of run. I am able to provide a shell
script for preventing this, if one were to request it.
In addition, the "View Report" feature could
theoretically be used to launch code embedded in a
modified session file, to the same effect as the asbove
deficiency. I have no idea as to how one could prevent
such malicious execution of code. I will compile a list
of web browsers avaliable for Linux, and post the in a
later comment as well.
Logged In: YES
user_id=1524933
I understand your consern about dialog requesting web
browser command. But the problem is that i had no choice to
open a web browser other then atempt to run all browser
commands. I implemented only gnome-open command and if it
fails it will ask user to enter his command. Either that or
no report preview at all.
But i don't see any potential security hazard here.
You said:
"Any person with physical access to the terminal on which
TimeSaver is running may be able to do harm to the system ."
Yes, but not because TimeSaver has security problem, I
think it's because the person has physical access to the
terminal :)
The second potential risk you mentioned is: "loading .xml
files for reports on a given session". I really don't see
no risk here. All program does is reading text from xml
file and creates session and task objects.
Btw, report view doesn't load anything. It just saves
session to xml file and runs web browser with that file as
an argument.
But OK i will implement more web browser commands, that is
not such a problem.
Thank you for report