F5-K000160663: Low severity F5 BIG-IP Next SPK vulnerability
Moby is an open source container framework developed by Docker Inc. that is distributed as Docker Engine, Mirantis Container Runtime, and various other downstream projects/products. A firewalld vulnerability affects Moby releases before 28.0.0. When firewalld reloads, Docker fails to re-create iptables rules that isolate bridge networks, allowing any container to access all ports on any other container across different bridge networks on the same host. This breaks network segmentation between containers that should be isolated, creating significant risk in multi-tenant environments. Only containers in --internal networks remain protected. Workarounds include reloading firewalld and either restarting the docker daemon, re-creating bridge networks, or using rootless mode. Maintainers anticipate a fix for this issue in version 25.0.13.
Affected Software
Event History
Frequently Asked Questions
What is the severity of F5-K000160663?
The severity of F5-K000160663 is critical due to potential security risks associated with the firewalld vulnerability.
How do I fix F5-K000160663?
To fix F5-K000160663, upgrade Moby to version 28.0.0 or later to mitigate the identified vulnerabilities.
Which versions are affected by F5-K000160663?
F5-K000160663 affects various versions of BIG-IP Next SPK, CNF, and for Kubernetes prior to their specified secure versions.
What is the impact of F5-K000160663?
The impact of F5-K000160663 includes improper handling of iptables, potentially allowing unauthorized network access.
Who is affected by F5-K000160663?
Organizations using vulnerable versions of F5 BIG-IP Next SPK, CNF, and for Kubernetes are affected by F5-K000160663.