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

vCenter Server Appliance (and PSC) 6.x Workaround for vulnerabilities which require local access (52312)

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

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Purpose

The vCenter Server Appliance 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 vCenter Server Appliance (and PSC) 6.0, 6.5, and 6.7. Do not apply this workaround to other VMware products.

Functionality Impacts

All users with roles of “Operator” may not be able to perform actions that were previously possible while the workaround is in place. This is the only functionality impact known at the time of publishing this article.

Resolution

To work around this issue run one of these.

Workaround 1

Remove access to the appliance shell for non-root users:
Note: These steps must not be applied to service account users: root, sso-user, dnsmasq

Login to the vCenter Server Appliance with an SSH session and the root user.

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

cp /etc/passwd /etc/passwd.bkup

To list all users, run this command in the appliance shell and take note of the users listed:

user.list

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

vi /etc/passwd

Search for all non-root users who have operator access.

For example the user test has access to appliancesh.

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

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

For example:

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

Save and exit the file

To confirm that the workaround run these steps:

Attempt to log into vCenter Server Appliance using SSH and user with the Operator role.

Operator users should no longer be able to log in.

To remove the workaround run these following steps:

Login to the vCenter Server 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/appliancesh for all the Operator users.

For example:

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

Save and Exit the file

Workaround 2

Disable the bash shell on vCenter Server Appliance:

Login to the vCenter Server Appliance with an SSH session and the root user.

Change to the appliancesh shell by running this command:

# appliancesh

Login using the root username and password.

Run this command to disable bash shell:

shell.set –-enabled false

To validate the workaround run these following steps:

Login to the vCenter Server Appliance with an SSH session and a non-root user.

The login is successful and the appliancesh is launched.

Attempt to switch to the Bash shell by running the shell command.

All non-root users should not be able to switch to the Bash shell.

​Note: The default shell is the Appliance Shell unless manually changed to Bash/Nologin. for more information, see Toggling the vCenter Server Appliance 6.x default shell.

To remove the workaround run these steps:

Login to the vCenter Server Appliance with an SSH session and the root user.

Run this command to enable the bash shell:

shell.set –-enabled true

Example vulnerabilities that this workaround will be effective against:

CVE-2017-5753

CVE-2017-5715

CVE-2017-5754

Related Information

简体中文：vCenter Server Appliance（和 PSC）6.5/6.0 针对要求本地访问的漏洞的权宜措施

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server Appliance

Related Versions:

VMware vCenter Server Appliance 6.7.x

VMware vCenter Server Appliance 6.5.x

VMware vCenter Server Appliance 6.0.x

Take Our Survey

Support Assistant