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

vCloud Usage Meter 3.5 / 3.6 - Workaround for vulnerabilities which require local access (52467)

Last Updated: 5/4/2018Categories: TroubleshootingTotal Views: 7105Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Purpose

The vCloud Usage Meter team has investigated the impact 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 and permanent fixes will be released as soon as they are available.

Warning

This workaround is applicable ONLY to vCloud Usage Meter 3.5, 3.6, and 3.6.1. Do not apply this workaround to other VMware products.

Functionality Impacts

This workaround is only necessary for users who have enabled SSH to perform upgrade data migration. By default, SSH is disabled and this workaround is not needed. However, if you have enabled SSH per documentation to perform a data migration, then use these steps to disable SSH.

No metering functions will be impacted by the workaround. If you need to perform a data migration from the affected Usage Meter, then follow the documentation to enable SSH, and upon completion of migration, follow this workaround to disable SSH.

Resolution

To implement the workaround for vulnerabilities which require local access, perform the following best steps:

Log in via SSH or console as user usgmtr, then run su and enter the root password to become the root user.

Once logged in as the root user, run the following command:

/usr/sbin/service sshd stop

/usr/sbin/chkconfig sshd off

To confirm that the workaround has been correctly applied perform the following steps:

Try to log in from any other machine using SSH to the above server. For example: ssh usgmtr@hostname and it will say that connection is refused.

To revert the workaround:

Log in via console as user usgmtr, then run su and enter the root password to become the root user.

Once logged in as the root user, run the following command to enable SSH:

/usr/sbin/service sshd start

If you want to enable SSH when you reboot Usage Meter appliance, run the following command:

/usr/sbin/chkconfig sshd on

Please note that enabling SSH is not required for normal operations of Usage Meter. It is only required for data migration.

Example vulnerabilities that this workaround will be effective against:

CVE-2017-5753, CVE-2017-5715, CVE-2017-5754

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

KB
•
适用于分支目标注入的管理程序辅助客户机缓解方法 (52085)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCloud Usage Meter

Related Versions:

VMware vCloud Usage Meter 3.6.x

VMware vCloud Usage Meter 3.5.x

Take Our Survey

Support Assistant