kubernetes: Incorrect rule injection in CNI portmap plugin
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 7 Extras | |||
| containernetworking-plugins-0:0.7.5-2.el7 | cpe:/a:redhat:rhel_extras_other:7 | RHBA-2019:0862 | 2019-04-23T00:00:00Z |
| Red Hat Enterprise Linux 8 | |||
| container-tools:rhel8-8010020190927090915.4985cc55 | cpe:/a:redhat:enterprise_linux:8 | RHSA-2019:3403 | 2019-11-05T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2019-19300 | 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. |
No CVSS v4.0
No CVSS v3.1
This CVE is not in the KEV list.
Exploit prediction score: 3.2% (3.159% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.