Hi all,

An XSS issue has been discovered and fixed in the filebrowser_safe package.
You should be able to upgrade seamlessly right away (pip install -U
filebrowser_safe). In many areas throughout filebrowser, querystring
parameters are passed directly into templates to form URLS for links and
forms, and these were not being escaped correctly, therefore allowing
arbitrary JavaScript code to be injected. In order to exploit this, a
malicious user would need to trick an authenticated administrator into
clicking a malicious link or viewing a malicious web page containing the
XSS payload. If for some reason you're unable to upgrade seamlessly, here
is the fix which you need to apply:

https://github.com/stephenmcd/filebrowser-safe/commit/14b30017d27ca6a952e1578ed8cecbb102979967

In the new release, I've also included a change that now ensures files
uploaded must match the `FILEBROWSER_EXTENSIONS` setting. This setting was
previously only used client-side and not validated server-side. This was
reported as a security issue along with the XSS issue above. It's worth
noting that the maintainers of the original filebrowser package have
previously deemed this as not an issue, so that's something to keep in mind
before rehashing the debate around maintaining a fork.

Thanks to John Page (hyp3rlinx) for reporting the issue privately.


-- 
Stephen McDonald
http://jupo.org

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to