Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

vRealize Automation Appliance 7.x Workaround for vulnerabilities which require local access (52377)

Last Updated: 6/16/2020Categories: SecurityTotal Views: 8747Language:
JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

The vRealize Automation team has investigated the impact of vulnerabilities which require local access (such as local privilege escalation, local information disclosures, local denial of service, etc.) and determined that the product can be protected from these types of vulnerabilities by performing the steps detailed in this article. This workaround is meant to be a temporary solution only.

Warning:

This workaround is applicable ONLY to vRealize Automation Appliance 7.x. Do not apply this workaround to other VMware products.

This workaround must be applied to all vRealize Automation appliances in High Availability deployments.

Functionality Impacts:
Workaround 1: All non-root custom users identified in the resolution section may not be able to perform actions that were previously possible while the workaround is in place due their disabled SSH access.

Workaround 2: All users, including root, may not be able to perform actions that were previously possible while the workaround is in place due to disabled SSH service.

Resolution

Please see the Workaround section.

Workaround

To implement the workaround for perform one of the following:

Workaround 1

Remove access to the appliance shell for non-root users:

Login to the vRealize Automation Appliance with a SSH session and the root user.

Backup the /etc/passwd file with this command:

cp /etc/passwd /etc/passwd.bkup

Download the 52377_identify_non_root_users.py.gz script.

Extract and transfer the script to the appliance.

Run this command to make sure that the script is executable:

chmod 755 identify_non_root_users.py

To list all the non-root custom users, run this command and take note of the users listed

python identify_non_root_users.py

If there are no users listed in the console, there are no users to disable.

Open the /etc/passwd file with a plain text editor using this command:

vi /etc/passwd

Search for all non-root users identified in step 6.

For example the user test has access to bash.

test:x:1020:100:test:/home/test:/bin/bash

Change the default shell access from /bin/bash to /sbin/nologin.

For example:

test:x:1020:100:test:/home/test:/sbin/nologin

Save and exit the file.

To confirm that the workaround works, run these steps:

Attempt to log into vRealize Automation Appliance using SSH and with a non-root user from step 6.

Non-root users should no longer be able to log in.

To remove the workaround, run these following steps:

Login to the vRealize Automation Appliance with an SSH session and the root user.

Backup the /etc/passwd file by with this command:

cp /etc/passwd /etc/passwd.modified.bkup

Change the default shell access from /sbin/nologin to /bin/bash for all the non-root users.

For example:

test:x:1020:100:test:/home/test:/bin/bashsh

Save and Exit the file

Workaround 2

Disable the SSH shell on vRealize Automation Appliance:

Login to the vRealize Automation Appliance with an SSH session and the root user.

Once logged in, run these commands:

/etc/init.d/sshd stop

chkconfig sshd off

To validate the workaround run these following steps:

Try to log in from any other machine using SSH to the appliance.

It should prompt that connection is refused.

To remove the workaround run these steps:

Log in from the vSphere console as root.

Start the ssh service with the command /etc/init.d/sshd start.

Run the command chkconfig sshd on.

Example vulnerabilities that this workaround will be effective against:

CVE-2017-5753

CVE-2017-5715

CVE-2017-5754

Related Information

简体中文：vRealize Automation 设备 7.2/7.3/7.4 针对要求本地访问的漏洞的解决办法

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

52377_identify_non_root_users.py.gz

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Aria Automation

Related Versions:

VMware vRealize Automation 7.6.x

VMware vRealize Automation 7.5.x

VMware vRealize Automation 7.4.x

VMware vRealize Automation 7.3.x

VMware vRealize Automation 7.2.x

Take Our Survey

Support Assistant