The risk is real, my own server was compromised yesterday.
http://news.softpedia.com/news/Unpatched-OpenX-Vulnerability-Exploited-to-Compromise-Multiple-Ad-Servers-156402.shtml
I am in the process of creating an updated port, should file a pr soon,
but it should be marked as forbidden until then.
16.09.2010 19:19, Ruslan Mahmatkhanov пишет:
16.09.2010 17:59, Dan Langille пишет:
On Thu, September 16, 2010 1:09 am, Ruslan Mahmatkhanov wrote:
16.09.2010 05:45, Dan Langille пишет:
This came in last night: http://blog.openx.org/09/security-update/
Port needs to be upgraded to 2.8.8 a
16.09.2010 17:59, Dan Langille пишет:
On Thu, September 16, 2010 1:09 am, Ruslan Mahmatkhanov wrote:
16.09.2010 05:45, Dan Langille пишет:
This came in last night: http://blog.openx.org/09/security-update/
Port needs to be upgraded to 2.8.8 and a vuln entry created Sorry,
bags not me
On Thu, September 16, 2010 1:09 am, Ruslan Mahmatkhanov wrote:
> 16.09.2010 05:45, Dan Langille пиÑеÑ:
>> This came in last night: http://blog.openx.org/09/security-update/
>>
>> Port needs to be upgraded to 2.8.8 and a vuln entry created Sorry,
>> bags not me.
>>
>
> Until update is not
16.09.2010 05:45, Dan Langille пишет:
This came in last night: http://blog.openx.org/09/security-update/
Port needs to be upgraded to 2.8.8 and a vuln entry created Sorry,
bags not me.
Until update is not come up, user can apply this workaround:
echo "RemoveType .php" > www/images/.htacc