Storing datacenter Nedzone 30-10-2014 van ca. 16.00 - 16.15 uur

16.35 uur (update)
Netwerkproblemen van zojuist werden veroorzaakt door een grootschalige DDoS aanval op het Nedzone datacenter, op dit moment wordt het verkeer gefilterd en is het netwerk weer normaal bereikbaar. Het netwerk zal de komende uren extra in de gaten worden gehouden.

16.15 uur
Door een nog onbekende storing op het datacenter Nedzone waren de servers niet bereikbaar voor ca. 15 minuten, helaas weten wij de juiste oorzaak nog niet. Zodra deze bent is zullen wij u verder informeren. (via Twitter is de informatie en status gemeld)

Onze excuses voor de ontstane overlast.

Joomla & Akeeba security leaks september 2014

Joomla security leaks:
Gelieve een en ander per onmiddelijk te patchen cq upgraden zie:
http://developer.joomla.org/security.html

• Akeeba Backup for Joomla! Professional, version 3.0.0 up to and including 4.0.2
• Akeeba Backup Professional for WordPress, 1.0.b1 up to and including 1.1.3
• Akeeba Solo, 1.0.b1 up to and including 1.1.2
• Admin Tools Core and Professional, version 2.0.0 up to and including 2.4.4. Later versions are not affected as they do not include the Joomla! update feature.
• Akeeba CMS Update, version 1.0.a1 up to and including 1.0.1
• Joomla! 2.5, 3.0, 3.1, 3.2, 3.3 up to and including 3.3.4

zie hier: https://www.akeebabackup.com/home/news/1605-security-update-sep-2014.html

Er is in het ‘bash’-package voor Linux/Unix een kritieke kwetsbaarheid gevonden (25 september CVE-2014-7169 en 26 september CVE-2014-6271).

Deze kwetsbaarheid maakt het mogelijk om een eventueel kwaadaardige code uit te voeren op een server.

Voor alle klanten die servers in gebruik hebben met CentOS 5 of 6 zijn de genoemde updates gisteren en vandaag uitgevoerd.....

We want to alert you to a serious vulnerability in the WordPress Slider Revolution premium plugin. The developer behind the popular plugin patched the vulnerability silently, meaning that, if you are running WordPress Slider Revolution, you have probably not yet heard that you must update as soon as possible.
 
This is a very serious vulnerability known as a Local File Inclusion (LFI) attack. It allows a user to retrieve data from files on your server. An example of such an attack would be pulling your WordPress wp-config.php file and using the credentials in that file to exploit your database and gain access to your website. If you use this plugin, please update immediately.

Hier een link van een overzicht welke themes zijn geinfecteerd:
http://marketblog.envato.com/general/affected-themes/

We herhalen het nog maar eens!

The bruteforce attacks against WordPress and Joomla login pages - as written here already: https://www.helpburo.eu/index.php?/News/NewsItem/View/67/massale-brute-force-pogingen-op-wordpress-sites - are getting worse all over the internet, not only on your server.

Even worse are the WordPress xmlrpc pingback attacks which are well known
since years - see here a description and also a solution to this
problem: http://perishablepress.com/wordpress-xmlrpc-pingback-vulnerability/

The problem is, that the attacks are coming from thousands of IPs in parallel, which even overloads those plug-ins. There exists currently only one solution:

1) Joomla installations
Use Plesk or DirectAdmin frontend to password-protect the directory /administrator of the Joomla installation

2) WordPress installations
For WordPress, we must password-protect the access to the file wp-login.php, as this one is opened directly by the attackers. This must be done manually:

a) create a .htpasswd file, either manually on the server or with an online tool like http://www.htaccesstools.com/htpasswd-generator/
b) place the .htpasswd file in the base directory of your WordPress installation
c) create in the base directory of your WordPress installation a .htaccess file with the following lines - if already a .htaccess file exists, add those lines to the absolute top of the file:

# Stop Apache from serving .ht* files

Order allow,deny
Deny from all


# Protect wp-login

AuthUserFile /YYYYY/.htpasswd
AuthName "Private access"
AuthType Basic
require user XXXXX




- replace the XXXXX with the username you used in the .htpasswd file.
- replace /YYYYY with the full path to your hosting directory, eg:
  /var/www/vhosts/testdomain.nl/httpdocs/.htpasswd   (Plesk style)
  /home/user/domains/testdomain.nl/public_html/.htpasswd  (DirectAdmin style)

For server owners:

THIS MUST BE DONE FOR ALL WORDPRESS OR JOOMLA INSTALLATIONS ON THE SERVER!