From: Karl Dahlke <email@example.com>
Subject: [Edbrowse-dev] zip and security
Date: Mon, 05 Mar 2018 17:17:50 -0500 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
Here is something funny, so terribly unlikely that I'm not gonna worry about it, but there's always a way, isn't there.
Suppose Fred knows all about edbrowse, and millions of people are using edbrowse (instead of 15),
and he knows a lot of us use the plugins in the wiki to access zip files.
Or maybe the script traverses the entire tree in the zip archive and sends all the files to the server.
Now I say it's unlikely because the web page would have to know the name of your zip file, i.e. the path to your zip file, and at least one directory.
In my example it has to know there is foo.zip in your current directory and it has a directory inside it called top.
There aren't any standard zip files in standard places on unix machines, so I guess we're all right.
I just looked under /bin /lib /usr /etc and found none.
next reply other threads:[~2018-03-05 22:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 22:17 Karl Dahlke [this message]
2018-03-05 22:32 ` Dominique Martinet
2018-03-05 23:35 ` Kevin Carhart
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).