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 PKS upgrade approach for CRITICAL CVE : 2019-3779 (67116)

Last Updated: 2/14/2019Categories: SecurityTotal Views: 2141Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Details

VMware PKS versions 1.3.1 and earlier are effected by Common Vulnerabilites and Exposure (CVE) 2019-3779. PKS is addressing this issue by providing a series of patch releases that will update all Certificate Authority (CA) certificates for v1.2.X and 1.3.X.  This article describes the CVE and the process for upgrading your PKS installation.

This article describes the CVE and the process for upgrading your VMware PKS installation.

Cause:

PKS deployed Kubernetes clusters, created in VMware PKS versions prior to v1.3.1, trust the same CA used by the Kubernetes API to sign and trust certs for Etcd.

This could allow a user authenticated with a cluster to request a signed certificate leveraging the Kubernetes CSR capability to obtain a credential that could allow privileged access to Etcd.

Solution

To prevent this scenario, it is recommended to provision Kubernetes clusters with a dedicated CA for Etcd certificate trust chain.

PKS v1.3.2 and v1.2.9 implements this recommendation by default.

In order to replace the Etcd CA and reduce the impact to running workloads on clusters provisioned by previous versions of PKS, environments being upgraded must execute the following three phase sequence and upgrade all errands during each phase.

Phase I. Introduce a dedicated Etcd CA during new cluster creations or cluster upgrades. Clusters will trust both the new CA and the existing Kubernetes API CA.

Phase II. Regenerate Etcd Certificates signed by the new Etcd CA during new cluster creations or cluster upgrades. Clusters will trust both the new CA and the existing Kubernetes API CA.

Phase III. Remove the trust designation for the existing Kubernetes API CA during new cluster creations or cluster upgrades.

NOTE:  These Phases MUST be accomplished in succession in order to reduce the impact to deployed clusters with workloads and to address the CVE.  The image above depicts valid upgrade paths to ensure the CVE is addressed and the risk to running workloads is red.

Important upgrade notes:

The image above depicts valid upgrade paths to ensure the CVE is appropriately addressed and the risk to running workloads is reduced.

It is STRONGLY recommended to upgrade to PKS v1.2.9 or PKS v1.3.2  to resolve this CVE.

Regardless of branch version, these Phases MUST be accomplished in succession. For example, v1.2.8 must be upgraded to v1.2.9 or v1.3.2.

Upgrading from v1.3.0 to v1.3.2 is not supported, v1.3.0 has been removed from download access.

You can choose to upgrade from 1.2.x to 1.3.x builds as long as PHASE order is maintained. For example, upgrading from v1.2.7 to v1.3.1 to v1.3.2. Doing so will help to ensure that the CVE is addressed and reduce impact to running workloads.

The CVE will be fully addressed only when all 3 phases have been applied in sequence.

Choosing to perform new installs directly with a phase II build still requires you to upgrade to a phase III build. For example, a new install with v1.3.1 must upgrade to v1.3.2.

You can choose to perform a new install directly to a phase III build or newer to address this CVE. For example, a new Install with v1.2.9 or v1.3.2 or greater is OK.

If you wish to remain on v1.2.x builds, you must start the upgrade path from v1.2.5 through v1.2.7, and complete phases II & III appropriately.

Related Information

https://community.pivotal.io/s/article/pks-upgrade-approach-for-critical-cve

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
VMware 响应 Intel 处理器中的矢量寄存器采样 (CVE-2020-0548) 和 L1D 逐出采样 (CVE-2020-0549) 推理执行漏洞 (76949)

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 PKS

Related Versions:

VMware PKS 1.x

Take Our Survey

Support Assistant