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

VMware response to ‘L1 Terminal Fault’ (L1TF) Speculative-Execution vulnerabilities in Intel processors for VMware SaaS offerings: CVE-2018-3646 and CVE-2018-3620 (55808)

Last Updated: 3/21/2024Categories: SecurityTotal Views: 26939Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Purpose

The purpose of this article is to provide a response to the security issues related to speculative execution in Intel processors described by CVE-2018-3646 (L1 Terminal Fault - VMM) and CVE-2018-3620 (L1 Terminal Fault - OS) as they apply to VMware SaaS offerings.

Responses have been broken into the following categories for potentially affected offerings. The scope of this document is limited to VMware SaaS offerings that run in a vSphere environment.

Infrastructure security impact statement

Recommended actions

Operational impact statement

The Update History section of this article will be revised when there is a significant change to this document. Click Subscribe to Article in the Actions box to be alerted when new information is added to this document and sign up at our Security-Announce mailing list to receive new and updated VMware Security Advisories. In addition, operational events are announced for our various SaaS offerings on our VMware Cloud Services Status Page.

This article is dedicated to VMware SaaS offerings, for an overview of these vulnerabilities and links to on-prem product documentation please see KB55636.

Note: this document uses terminology defined in KB55806.

Resolution

VMware Cloud on AWS (Including MSPs)

Infrastructure security impact statement:

CVE-2018-3646 (L1 Terminal Fault - VMM)

VMware Cloud on AWS has completed the mitigation process for CVE-2018-3646.

CVE-2018-3620 (L1 Terminal Fault - OS)

Based on current evaluations, CVE-2018-3620 does not affect the VMware Cloud on AWS infrastructure itself.

Recommended customer actions:

CVE-2018-3646 (L1 Terminal Fault - VMM)

No customer action required.

CVE-2018-3620 (L1 Terminal Fault - OS)

3rd party operating systems and VMware appliances deployed in an Organization’s SDDC may be affected by CVE-2018-3620. For information on VMware appliances please see KB55807. Customers are advised to contact their 3rd party operating system vendor to determine appropriate actions for mitigation of CVE-2018-3620.

Operational impact statement

Customers should not experience any unscheduled operational impacts to their Organization’s SDDC. Please use the in-product support center to file an SR or chat support for any questions or concerns.

VMware Workspace One SaaS (formerly Airwatch Saas)

Infrastructure security impact statement:

CVE-2018-3646 (L1 Terminal Fault - VMM)

Based on current evaluations, VMware Workspace One SaaS infrastructure is not impacted by CVE-2018-3646.

CVE-2018-3620 (L1 Terminal Fault - OS)

Based on current evaluations, the VMware Workspace One SaaS infrastructure is not impacted by CVE-2018-3620.

Recommended customer actions:

CVE-2018-3646 (L1 Terminal Fault - VMM)

No customer action required.

CVE-2018-3620 (L1 Terminal Fault - OS)

No customer action required.

Operational impact statement

Customers should not experience any unscheduled operational impacts.

VMware Horizon Cloud

Infrastructure security impact statement:

CVE-2018-3646 (L1 Terminal Fault - VMM)

VMware Horizon Cloud is affected by CVE-2018-3646 but due to environmental factors the severity of the issue is lowered to Moderate from Important. The VMware Horizon Cloud infrastructure is architected to segment customer environments from one another, therefore, inter-organizational leaks between virtual machines are not possible as different organizations do not share ESXi hosts. Updates to are being prioritized to resolve CVE-2018-3646.

CVE-2018-3620 (L1 Terminal Fault - OS)

Based on current evaluations, the VMware Horizon Cloud infrastructure is not impacted by CVE-2018-3620.

Recommended customer actions:

CVE-2018-3646 (L1 Terminal Fault - VMM)

No customer action required.

CVE-2018-3620 (L1 Terminal Fault - OS)

Virtual Desktops may be affected by CVE-2018-3620. Customers are advised to contact their 3rd party operating system vendor to determine appropriate actions for mitigation of CVE-2018-3620.

Operational impact statement

After maintenance is performed by VMware, which should by itself have no operational impact to their Organization's SDDC, customers will no longer be able to publish images until they have upgraded VMware Tools in their images to version 10.2.5 or above. Customers will not experience any impact with use of already provisioned VMs and published images. VMware will notify customers once updates are complete so that you may perform upgrades of VMTools in your images.

Related Information

Find out more about L1 Terminal Fault (L1TF) here

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

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:

Datacenter

Related Versions:

Take Our Survey

Support Assistant