Homepage

Improper Enforcement of Behavioral Workflow Affecting podman-docker package, versions <0:1.4.2-5.module+el8.1.0+4240+893c1ab8

Severity

 Recommended
high

Based on CentOS security rating.

Threat Intelligence

EPSS
0.23% (63rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Improper Enforcement of Behavioral Workflow vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CENTOS8-PODMANDOCKER-1995778
  • published26 Jul 2021
  • disclosed28 Mar 2019
Report a new vulnerability Found a mistake?

Introduced: 28 Mar 2019

CVE-2019-9946  (opens in a new tab)
CWE-841  (opens in a new tab)

How to fix?

Upgrade Centos:8 podman-docker to version 0:1.4.2-5.module+el8.1.0+4240+893c1ab8 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream podman-docker package and not the podman-docker package as distributed by Centos. See How to fix? for Centos:8 relevant fixed versions and status.

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.

References