Homepage

Always-Incorrect Control Flow Implementation Affecting container-tools:1.0/oci-systemd-hook package, versions <1:0.1.15-2.git2d0b8a3.module_el8.3.0+2044+12421f43

Severity

 Recommended
0.0
high
0
10

Based on AlmaLinux security rating.

Threat Intelligence

EPSS
0.21% (60th 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 IDSNYK-ALMALINUX8-CONTAINERTOOLS-5631567
  • published28 May 2023
  • disclosed5 Nov 2019
Report a new vulnerability Found a mistake?

Introduced: 5 Nov 2019

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

How to fix?

Upgrade AlmaLinux:8 container-tools:1.0/oci-systemd-hook to version 1:0.1.15-2.git2d0b8a3.module_el8.3.0+2044+12421f43 or higher.
This issue was patched in ALSA-2019:3403.

NVD Description

Note: Versions mentioned in the description apply only to the upstream container-tools:1.0/oci-systemd-hook package and not the container-tools:1.0/oci-systemd-hook package as distributed by AlmaLinux. See How to fix? for AlmaLinux: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