Approved changes feed: RSS · Atom
cpe:2.3:a:cncf:portmap:*:*:*:*:*:container_networking_interface:*:*
part: a version: * update: *
| Vendor | Cncf (2ee90faf-978f-5e65-8538-ffa11f7df136) |
|---|---|
| Product | Portmap (9a6c1c70-6f4c-5f59-9ee6-ccacda21687d) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | container_networking_interface |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2019-9946 |
vulnerable | 2026-06-08 05:14:26.634384 |
Details available
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.
Published: 2019-04-02T17:22:52.000Z
Updated: 2024-08-04T22:10:08.508Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.