Re: a vulnerability in dillo
On Sun, 2 Mar 2003, Ivan Popov wrote:
Hello,
having read the statement about dillo being a secure browser,
It tries to be!
I want to draw your attention to the exploitable in different ways bookmarks plugin interface.
I submitted it as a bug and mentioned denial-of-service only, but creating predictably named sockets in /tmp opens to other possible attacks (e.g. spoofing your bookmarks) as well.
I realize dillo and the plugins are evolving at fast rate, but this issue can (and should?) be fixed even on the early stages of development.
Probably (soon) socket file descriptors will reside in /tmp/dillo and use temporary filenames, or something akin (this also solves the problem of a pre-existent file with the same name).
Thanks for the great software! I appreciate dillo - it is small, fast and functional.
Thanks for your nice comments too. Cheers Jorge.-
Hello Jorge, thanks for your answer! On Wed, 5 Mar 2003, Jorge Arellano Cid wrote:
Probably (soon) socket file descriptors will reside in /tmp/dillo and use temporary filenames, or something akin (this
My first reaction is - who would be responsible for creating that /tmp/dillo? The first user? probably not. root at host startup? not a good idea to rely on the host admin to be able to run a program. May be something like /tmp/dillo-<truly-random-chars>/ per dillo instance, then you are rather safe against tampering but you have to make your bookmark server aware of possible parallel server accessing the same bookmarks. I would suggest not to rely on a common name all dillo instances of the same user would share. Then it would be 1. widely known and open to tampering 2. not working across different hosts anyway, as you need a server process per host, while bookmarks file may be shared between hosts. Just in case - I am glad you do not try to put sockets in/under homedirs. 1. the underlying filesystems may not support that 2. there is a hardcoded (in the specification) limit on the path name length of a unix socket - it breaks on some setups with homedirs deep in the filetree I mention it as it is a fairly often mistake of different software with unix sockets, to put sockets under the user's homedir. Best regards and thanks for dillo! -- Ivan
participants (2)
-
Ivan Popov -
Jorge Arellano Cid