We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
Critical vulnerability in bash
Critical vulnerability in bash
The critical vulnerability, which had been dormant in the OpenSSL software for a long time, made headlines with its severity and threatening potential, as security experts and popular sites scrambled to secure their servers and assure their users that their information was A-OK. Now another exploit, going by the name Shellshock, looks to pose a similar threat to machines worldwide. The impact looks to be even greater than Heartbleed’s: Where Heartbleed only affected some 500,000 machines in total, conservative estimates place Shellshock’s influence at over 500 million compromised machines. The main problem is the location of the vulnerability – a small piece of software called Bash, which stands for Bourne-Again SHell
http://so-l.ru/news/show/16961665
http://finance.yahoo.com/news/heartblee ... 3.html?l=1
Solution
CentOS
Debian/Ubuntu
http://so-l.ru/news/show/16961665
http://finance.yahoo.com/news/heartblee ... 3.html?l=1
Solution
CentOS
Code: Select all
yum update bash
Code: Select all
apt-get update
apt-get upgrade bash
Re: Critical vulnerability in bash
Thanks for the notice.
I was wondering... doesn't VestaCP handle critical updates automatically?
I'm comparing Virtualmin vs VestaCP right now and Virtualmin automatically updates if you activate such option from the admin panel.
Thank you.
I was wondering... doesn't VestaCP handle critical updates automatically?
I'm comparing Virtualmin vs VestaCP right now and Virtualmin automatically updates if you activate such option from the admin panel.
Thank you.
Re: Critical vulnerability in bash
did that first time update come out for ubuntu. Thanks for info anyway ;)