Описание
The CNI portmap plugin allows containers to emulate opening a host port, forwarding that traffic to the container. Versions 1.6.0 through 1.8.0 inadvertently forward all traffic with the same destination port as the host port when the portmap plugin is configured with the nftables backend, thus ignoring the destination IP. This includes traffic not intended for the node itself, i.e. traffic to containers hosted on the node. Containers that request HostPort forwarding can intercept all traffic destined for that port. This requires that the portmap plugin be explicitly configured to use the nftables backend. This issue is fixed in version 1.9.0. To workaround, configure the portmap plugin to use the iptables backend. It does not have this vulnerability.
A flaw was found in the CNI (Container Network Interface) portmap plugin. This vulnerability allows containers to intercept all traffic destined for a host port via inadvertent forwarding of traffic with the same destination port when the plugin is configured with the nftables backend, ignoring the destination IP.
Отчет
This vulnerability is rated Moderate for Red Hat because it allows containers to intercept non-local traffic when the CNI portmap plugin is explicitly configured to use the nftables backend. This issue affects CNI portmap plugin versions 1.6.0 through 1.8.0. Red Hat products are only affected if the nftables backend is specifically enabled for the CNI portmap plugin.
Меры по смягчению последствий
Configure the CNI portmap plugin to use the iptables backend instead of nftables. This can typically be achieved by modifying the CNI network configuration. After making this configuration change, services utilizing the CNI portmap plugin may require a restart or reload for the changes to take effect.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat Enterprise Linux 8 | container-tools:rhel8/containernetworking-plugins | Fix deferred | ||
| Red Hat Enterprise Linux 9 | containernetworking-plugins | Fix deferred | ||
| Red Hat OpenShift Container Platform 4 | containernetworking-plugins | Fix deferred | ||
| Red Hat OpenShift Container Platform 4 | openshift4/container-networking-plugins-microshift-rhel9 | Fix deferred | ||
| Red Hat OpenShift Container Platform 4 | openshift4/microshift-bootc-rhel9 | Fix deferred | ||
| Red Hat OpenShift Container Platform 4 | openshift4/ose-container-networking-plugins-rhel8 | Fix deferred | ||
| Red Hat OpenShift Container Platform 4 | openshift4/ose-container-networking-plugins-rhel9 | Fix deferred | ||
| Red Hat OpenShift Virtualization 4 | container-native-virtualization/cnv-containernetworking-plugins | Fix deferred | ||
| Red Hat OpenShift Virtualization 4 | container-native-virtualization/cnv-containernetworking-plugins-rhel9 | Fix deferred |
Показывать по
Ссылки на источники
Дополнительная информация
Статус:
6.6 Medium
CVSS3
Связанные уязвимости
The CNI portmap plugin allows containers to emulate opening a host port, forwarding that traffic to the container. Versions 1.6.0 through 1.8.0 inadvertently forward all traffic with the same destination port as the host port when the portmap plugin is configured with the nftables backend, thus ignoring the destination IP. This includes traffic not intended for the node itself, i.e. traffic to containers hosted on the node. Containers that request HostPort forwarding can intercept all traffic destined for that port. This requires that the portmap plugin be explicitly configured to use the nftables backend. This issue is fixed in version 1.9.0. To workaround, configure the portmap plugin to use the iptables backend. It does not have this vulnerability.
The CNI portmap plugin allows containers to emulate opening a host port, forwarding that traffic to the container. Versions 1.6.0 through 1.8.0 inadvertently forward all traffic with the same destination port as the host port when the portmap plugin is configured with the nftables backend, thus ignoring the destination IP. This includes traffic not intended for the node itself, i.e. traffic to containers hosted on the node. Containers that request HostPort forwarding can intercept all traffic destined for that port. This requires that the portmap plugin be explicitly configured to use the nftables backend. This issue is fixed in version 1.9.0. To workaround, configure the portmap plugin to use the iptables backend. It does not have this vulnerability.
CNA Plugins Portmap nftables backend can intercept non-local traffic
Уязвимость сетевых плагинов CNI Plugins, связанная с раскрытием информации, позволяющая нарушителю получить несанкционированный доступ к защищаемой информации
6.6 Medium
CVSS3