RSS Feed
Latest Updates
Sep
25
Bash Vulnerability
Posted by Chris -'- Support Team on 25 September 2014 04:45 PM

Critical Bash updates
~~~~~~~~~~~~~

There is a critical CVE vulnerability affecting all versions of the bash package. This vulnerability could allow for arbitrary code execution. Certain services and applications allow remote unauthenticated attackers to provide environment variables, allowing them to exploit this issue. An attacker can provide specially-crafted environment variables containing arbitrary commands that will be executed on vulnerable systems under certain conditions.

You may find the details of the vulnerability from the following URL's:

http://centosnow.blogspot.com/2014/09/critical-bash-updates-for-centos-5.html

https://access.redhat.com/articles/1200223

http://askubuntu.com/questions/528101/what-is-the-cve-2014-6271-bash-vulnerability-and-how-do-i-fix-it

To test if your version of Bash is vulnerable to this issue, run the following command:

For Centos Server
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
To test if your version of Bash is vulnerable to this issue, run the following command:

$ env x='() { :;}; echo vulnerable'  bash -c "echo this is a test"

If the output of the above command looks as follows, then the bash is vulnerable. Please run the command (yum update bash)

vulnerable
this is a test

you are using a vulnerable version of Bash. The patch used to fix this issue ensures that no code is allowed after the end of a Bash function. Thus, if you run the above example with the patched version of Bash, you should get an output similar to:

$ env x='() { :;}; echo vulnerable'  bash -c "echo this is a test"
bash: warning: x: ignoring function definition attempt
bash: error importing function definition for `x'
this is a test
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

For Ubuntu Server
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

The fixed versions are 4.3-7ubuntu1.1, 4.2-2ubuntu2.2, and 4.1-2ubuntu3.1. You can perform this update using apt-get.

First, check your package version:

dpkg -s bash | grep Version

This will look up info on your bash package, and filter the output to only show you the version.

For example, I see:

wlan1-loopback% dpkg -s bash | grep Version
Version: 4.3-7ubuntu1.1

and can determine that I am not vulnerable.

If you are vulnerable, you should first grab the newest package lists:

sudo apt-get update && sudo apt-get install bash

The first step makes sure that you have the newest package list that includes the fixed version, and the second command installs the newest (fixed) version of bash.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

We will check this and will do the needful for the server's for which root access is allowed for us. For the server's which we do not
have root access or updated passwords in billing, please perform the above mentioned patching steps.

If you want us to perform this, kindly provide us the root access to server.

Thank you very much!

If you have any questions, please don't hesitate to open a ticket with our helpdesk , we will be happy to assist you.


Read more »



Aug
26
WordPress 3.9.2 Security Release
Posted by Chris -'- Support Team on 26 August 2014 09:18 AM

WordPress 3.9.2 is now available as a security release for all previous versions. We strongly encourage you to update your sites immediately.

This release fixes a possible denial of service issue in PHP’s XML processing, reported by Nir Goldshlager of the Salesforce.com Product Security Team. It  was fixed by Michael Adams and Andrew Nacin of the WordPress security team and David Rothstein of the Drupal security team. This is the first time our two projects have coordinated joint security releases.

WordPress 3.9.2 also contains other security changes:

  • Fixes a possible but unlikely code execution when processing widgets (WordPress is not affected by default), discovered by Alex Concha of the WordPress security team.
  • Prevents information disclosure via XML entity attacks in the external GetID3 library, reported by Ivan Novikov of ONSec.
  • Adds protections against brute attacks against CSRF tokens, reported by David Tomaschik of the Google Security Team.
  • Contains some additional security hardening, like preventing cross-site scripting that could be triggered only by administrators.

We appreciated responsible disclosure of these issues directly to our security team. For more information, see the release notes or consult the list of changes.

Download WordPress 3.9.2 or venture over to Dashboard → Updates and simply click “Update Now”.

Sites that support automatic background updates will be updated to WordPress 3.9.2 within 12 hours. (If you are still on WordPress 3.8.3 or 3.7.3, you will also be updated to 3.8.4 or 3.7.4. We don’t support older versions, so please update to 3.9.2 for the latest and greatest.)

Source : https://wordpress.org/news/2014/08/wordpress-3-9-2/


Read more »



May
4
eu6 is having an issue
Posted by Chris -'- Support Team on 04 May 2014 05:42 PM
== Update ==

We had chasis/motherboard/cpu/ram replacement as a temp. and we will have another replacement soon.
Server is up and working fine now.

We do apologize for inconvience caused to you

==============================

Hello,

eu6 suddenly went down and we are having hardware issue causing kernel panic at boot.
Datacenter technicians are looking into issue.

We will keep you updated.

Thanks for your patience.


Read more »



Feb
13
Urgent Maintenance Needed : Seo25
Posted by Chris -'- Support Team on 13 February 2013 06:51 PM
Dear Valued Customers,

Seo25 had an issue with ram sticks and we needed to replace it.
Replacement is done and server is back online.

Thanks for your cooperation.


Read more »



Jan
7
An Important Security Announcement For WordPress Users:
Posted by Chris -'- Support Team on 07 January 2013 03:50 PM
This is to inform that a serious security hole has been found in wordpress plugin 'w3total cache'. Since directory listings were enabled on the cache directory, anyone could easily download all the database cache keys (wp-content/plugins/w3tc/dbcache), and extract details containing sensitive information, such as password hashes. Inorder to overcome this security issue you have to go to the wp-content directory of every WordPress install where this plugin is installed, and create a file named .htaccess inside the 'w3tc' directory with contents as below.

Order Allow,Deny
Deny from all


This will prevent outside access to the directory containing sensitive information. Also please be sure to update all WordPress installs and plugins to the latest version.


Read more »