Skip to main content

Solution and Step to fix CVE-2019-5736 Vulnerability - Docker

Recently a new vulnerability has been discovered in the the internet market having target to Docker services.

What is this Vulnerability:


In short, Docker service uses another service called as runc which is container run time to spawn and run containers. which simply means if docker task is to create docker images then runc task would be running them and attaching a process to container.

So as per the recent discovery by the maintainers of runc, the code of this service was having some bug which can be used by attackers to gain the root level of access of the host machine on which docker containers are running.



How it can be Exploited:


This vulnerability can be exploited in two ways (1) if the docker images are in use is vulnerable making the containers build from it vulnerable also (2) if somehow attacker got the access of containers and then trying to exploit using the bug present in runc and trying to get root privileges.


Solution to Fix Vulnerability:


Centos/Redhat



  • Update the docker version to latest version 18.09.2
           Example: docker-ce-18.09.2

AWS


  • Update the docker version to latest version 18.06.1ce
           Example:docker-18.06.1ce-7.25.amzn1



Note: For AWS environment, you might need to disable /etc/yum/pluginconf.d/update-motd.conf file by changing it to Zero "0" from One "1" to view the available AWS package.


Recommended Step:


Along with package update , we should also consider deploying containers using some random users rather than root user as the vulnerability gets exploited when having “UID 0” i.e root privileges inside container.

So when you are using composer file to define images, make sure to define some unique users to run those containers and which also need to present on server on which this containers need to run.

====================================X============X=================================================

Contact support@linuxforeveryone for any Freelancing work on Linux Servers

Subscribe my YouTube Channel 

Like My Facebook Page 

Browse the Best in class Web Hosting Plans



Linuxforeveryone started with the focus of solving linux related issues a sys admin faces everyday. So as System Admin whatever i learn through my experience i try to write it down for rest of opensource community.

If you appreciate what you have read or this blog writeup helped you can considering buying me COFFEE, this will help me keep writing and helping community further.

   

Comments

  1. Jackpot City Casino Web | Up to £10 Casino Welcome Bonus
    Jackpot titanium tubing City Casino, one of 바카라 the UK's best-known 우리 카지노 더킹 online casinos and 메리트 카지노 도메인 poker sites, is a part of 카지노 사이트 신고 the famous Slots City family.

    ReplyDelete

Post a Comment

Popular posts from this blog

How to Generate CSR using Openssl in Linux

Before Generating CSR ,let see what is Openssl. It is nothing but a core library ,which is used for general purpose in cryptography,it is an open source product which work towards the implementation of SSL and TLS protocols. Talking about openssl, some people called the certificates generated from openssl as "self signed certificate". lets go towards now,creating CSR and private key using openssl command, Just log in to any of your Linux box and run following command as  root user  replacing the required information as per your need . [root@SVR home]#   openssl req -new -newkey  rsa:2048 -nodes -sha256 -out domain_name.csr -keyout domain_name.key -subj "/C=US/ST=state/L=locality/O=organization/OU=organization unit Dept/CN=www.domain.com"  You will get output like : Then check whether ,all the information we have entered ,while creating CSR is proper ,by decoding the CSR from some online tool. First do the cat to the csr file [root@SVR home]# ...

Multiple instances of redis

In the last post I have covered how to install redis server on Centos/Rhel using rpm method and yum method and some troubleshooting skills. In this post i am going to cover how to install and configure redis to run with multiple ports.                                                                           But why we need more ports ? If you have read my earlier post , you already know that by default redis runs on single port 6379, which any one can use it for small website to cache the data. But for heavy website like magento we need to use additional ports along with 6379 to serve different cache from different ports. Like in Magento there is simple cache which is normally stored under /var/cache directory. Then there is Full Page Cache which is stored under /var/full_page_cache...