Bobcares

Sudo vulnerability CVE -2019-18634 – Avoid hacker gain server access

PDF Header PDF Footer

Are your servers a possible target of sudo vulnerability? Fix it now!

The latest sudo vulnerability CVE -2019-18634 allows hackers to execute commands as the root user. Here, it uses the sudo feature pwfeedback as the backdoor.

At Bobcares, we always strive to keep the servers secure against all the known vulnerabilities as part of our Server Management Services.

Today, let’s see how our Support Engineers deal with this sudo vulnerability.

 

What is this sudo vulnerability?

Let’s now check more details on the vulnerability reported with sudo on January 30, 2020.

This is the one that allows the attackers to gain access to our root privileges. Further,  the hacker can execute the programs with the security privileges of a superuser.

This is dangerous. The sudo package version from 1.7.1 to 1.8.30 is under risk. Fortunately, it affects servers that have the pwfeedback feature enabled.

The affected server list will be big since sudo is a default package that comes with most server distributions.

 

What is this pwfeedback option for?

Now comes the question of why we need a pwfeedback option in sudo.

This option is used for providing visual feedback for users. It prints an asterisk for each key when a user is inputting his password.

Unfortunately, “pwfeedback” works as the door for the hackers to enter on vulnerable servers.

Hackers make use of this option and trigger a stack-based buffer overflow in the privileged sudo process. Finally, the malicious attacker can execute any program they need just like the most privileged user on the server.

 

Is my server under risk?

Yes, maybe.

Luckily, there is no need to waste too much time to confirm the risk for the sudo package. Here is the way we use to check whether the servers are safe.

 

1. Check for pwfeedback option

As we already saw, it all depends on whether the server uses the pwfeedback option. If the pwfeedback option is set in your /etc/sudoers file, then yes your servers are at risk.

Upgrading the sudo package to 1.8.30 and above helps to tackle this vulnerability.

Today, let’s discuss how our Support Engineers mitigate sudo vulnerability and check whether our servers are safe.

We recently found that one of our customer’s server was under risk. We tested this by checking whether the pwfeedback option is enabled or not.

sudo -l

It was enabled and got an output like the one shown below:

sudo vulnerability

In such cases, we have to check our sudo version and confirm whether it is 1.8.30 or above.

 

2. Verify sudo version

Here, the customer was having an Ubuntu server. For checking the sudo version, we used the command below:

apt-cache policy sudo

sudo vulnerability

Here, the version shows as 1.8.21p2-3ubuntu1 with the pwfeedback enabled. Then, our Engineers confirmed that the server was at risk.

The solution here is to either disable the pwfeedback option or upgrade the server. As the customer wanted pwfeedback option enabled, we upgraded his server using:

sudo apt-get update

However, when the customer does not need the pwfeedback option, we always make sure to disable it in sudo by using the command,

visudo

Then we change:

Defaults pwfeedback

To:

Defaults !pwfeedback

That protects the server from the sudo vulnerability.

 

[Clueless about the sudo vulnerability status of your server? Our experts can help you.]

Conclusion

In short, we can resolve sudo vulnerability by disabling pwfeedback and upgrading the sudo package. Today we saw how our Support Engineers keep up the server against known vulnerabilities.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";
0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

server management

Spend time on your business, not on your servers.

TALK TO US

Or click here to learn more.

Speed issues driving customers away?
We’ve got your back!

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF