Cncf Cncf

Do you want an email whenever new security vulnerabilities are reported in any Cncf product?

Products by Cncf Sorted by Most Security Vulnerabilities since 2018

Cncf Envoy3 vulnerabilities

Cncf Harbor2 vulnerabilities

Cncf Spire2 vulnerabilities

Cncf Cni Network Plugins1 vulnerability

Cncf Portmap1 vulnerability

By the Year

In 2022 there have been 0 vulnerabilities in Cncf . Last year Cncf had 3 security vulnerabilities published. Right now, Cncf is on track to have less security vulnerabilities in 2022 than it did last year.

Year Vulnerabilities Average Score
2022 0 0.00
2021 3 7.37
2020 7 6.47
2019 1 7.50
2018 0 0.00

It may take a day or so for new Cncf vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.

Recent Cncf Security Vulnerabilities

An improper limitation of path name flaw was found in containernetworking/cni in versions before 0.8.1

CVE-2021-20206 7.2 - High - March 26, 2021

An improper limitation of path name flaw was found in containernetworking/cni in versions before 0.8.1. When specifying the plugin to load in the 'type' field in the network configuration, it is possible to use special elements such as "../" separators to reference binaries elsewhere on the system. This flaw allows an attacker to execute other existing binaries other than the cni plugins/types, such as 'reboot'. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability.

Directory traversal

In SPIRE before versions 0.8.5, 0.9.4, 0.10.2, 0.11.3 and 0.12.1, the "aws_iid" Node Attestor improperly normalizes the path provided through the agent ID templating feature, which may

CVE-2021-27099 6.8 - Medium - March 05, 2021

In SPIRE before versions 0.8.5, 0.9.4, 0.10.2, 0.11.3 and 0.12.1, the "aws_iid" Node Attestor improperly normalizes the path provided through the agent ID templating feature, which may allow the issuance of an arbitrary SPIFFE ID within the same trust domain, if the attacker controls the value of an EC2 tag prior to attestation, and the attestor is configured for agent ID templating where the tag value is the last element in the path. This issue has been fixed in SPIRE versions 0.11.3 and 0.12.1

AuthZ

In SPIRE 0.8.1 through 0.8.4 and before versions 0.9.4, 0.10.2, 0.11.3 and 0.12.1, specially crafted requests to the FetchX509SVID RPC of SPIRE Servers Legacy Node API can result in the possible issuance of an X.509 certificate with a URI SAN for a SPIFFE ID

CVE-2021-27098 8.1 - High - March 05, 2021

In SPIRE 0.8.1 through 0.8.4 and before versions 0.9.4, 0.10.2, 0.11.3 and 0.12.1, specially crafted requests to the FetchX509SVID RPC of SPIRE Servers Legacy Node API can result in the possible issuance of an X.509 certificate with a URI SAN for a SPIFFE ID that the agent is not authorized to distribute. Proper controls are in place to require that the caller presents a valid agent certificate that is already authorized to issue at least one SPIFFE ID, and the requested SPIFFE ID belongs to the same trust domain, prior to being able to trigger this vulnerability. This issue has been fixed in SPIRE versions 0.8.5, 0.9.4, 0.10.2, 0.11.3 and 0.12.1.

Improper Certificate Validation

A vulnerability was found in all versions of containernetworking/plugins before version 0.8.6

CVE-2020-10749 6 - Medium - June 03, 2020

A vulnerability was found in all versions of containernetworking/plugins before version 0.8.6, that allows malicious containers in Kubernetes clusters to perform man-in-the-middle (MitM) attacks. A malicious container can exploit this flaw by sending rogue IPv6 router advertisements to the host or other containers, to redirect traffic to the malicious container.

Fixed in v1.5.1, Argo version v1.5.0 was vulnerable to a user-enumeration vulnerability which

CVE-2020-11576 5.3 - Medium - April 08, 2020

Fixed in v1.5.1, Argo version v1.5.0 was vulnerable to a user-enumeration vulnerability which allowed attackers to determine the usernames of valid (non-SSO) accounts because /api/v1/session returned 401 for an existing username and 404 otherwise.

Information Disclosure

Cloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3

CVE-2019-19025 8.8 - High - March 20, 2020

Cloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 allows CSRF in the VMware Harbor Container Registry for the Pivotal Platform.

Session Riding

Cloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3

CVE-2019-19026 4.9 - Medium - March 20, 2020

Cloud Native Computing Foundation Harbor prior to 1.8.6 and 1.9.3 allows SQL Injection via project quotas in the VMware Harbor Container Registry for the Pivotal Platform.

SQL Injection

CNCF Envoy through 1.13.0 may consume excessive amounts of memory when proxying HTTP/1.1 requests or responses with many small (i.e

CVE-2020-8659 7.5 - High - March 04, 2020

CNCF Envoy through 1.13.0 may consume excessive amounts of memory when proxying HTTP/1.1 requests or responses with many small (i.e. 1 byte) chunks.

Resource Exhaustion

CNCF Envoy through 1.13.0 may consume excessive amounts of memory when responding internally to pipelined requests.

CVE-2020-8661 7.5 - High - March 04, 2020

CNCF Envoy through 1.13.0 may consume excessive amounts of memory when responding internally to pipelined requests.

Resource Exhaustion

CNCF Envoy through 1.13.0 has incorrect Access Control when using SDS with Combined Validation Context

CVE-2020-8664 5.3 - Medium - March 04, 2020

CNCF Envoy through 1.13.0 has incorrect Access Control when using SDS with Combined Validation Context. Using the same secret (e.g. trusted CA) across many resources together with the combined validation context could lead to the static part of the validation context to be not applied, even though it was visible in the active config dump.

AuthZ

Cloud Native Computing Foundation (CNCF) CNI (Container Networking Interface) 0.7.4 has a network firewall misconfiguration

CVE-2019-9946 7.5 - High - April 02, 2019

Cloud Native Computing Foundation (CNCF) CNI (Container Networking Interface) 0.7.4 has a network firewall misconfiguration which affects Kubernetes. The CNI 'portmap' plugin, used to setup HostPorts for CNI, inserts rules at the front of the iptables nat chains; which take precedence over the KUBE- SERVICES chain. Because of this, the HostPort/portmap rule could match incoming traffic even if there were better fitting, more specific service definition rules like NodePorts later in the chain. The issue is fixed in CNI 0.7.5 and Kubernetes 1.11.9, 1.12.7, 1.13.5, and 1.14.0.

Always-Incorrect Control Flow Implementation

Built by Foundeo Inc., with data from the National Vulnerability Database (NVD), Icons by Icons8. Privacy Policy. Use of this site is governed by the Legal Terms
Disclaimer
CONTENT ON THIS WEBSITE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. YOUR USE OF THE INFORMATION ON THE DOCUMENT OR MATERIALS LINKED FROM THE DOCUMENT IS AT YOUR OWN RISK. Always check with your vendor for the most up to date, and accurate information.