Security update for cni-plugins
This update of cni-plugins fixes the following issues: - rebuild the package with the go 1.21 security release (bsc#1212475).
- Update to 0.8.6-150100.3.20.1
PatchFirst · Latest vulnerabilities
Vulnerabilities published for cni-plugins in the last 30 days: 0. Listed in the KEV catalogue: 0.
Vulnerabilities: 7
This update of cni-plugins fixes the following issues: - rebuild the package with the go 1.21 security release (bsc#1212475).
This update of cni-plugins fixes the following issues: - rebuild the package with the go 1.21 security release (bsc#1212475).
This update of cni-plugins fixes the following issues: - rebuild the package with the go 1.20 security release (bsc#1206346).
This update of cni-plugins fixes the following issues: - rebuild the package with the go 1.19 security release (bsc#1200441).
This update for cni-plugins fixes the following issues: - CVE-2021-20206: Fixed arbitrary path injection via type field in CNI configuration (bsc#1181961).
This update for cni-plugins fixes the following issues: cni-plugins updated to version 0.8.6 - CVE-2020-10749: Fixed a potential Man-in-the-Middle attacks in IPv4 clusters by spoofing IPv6 router advertisements (bsc#1172410). Release notes: https://github.com/containernetworking/plugins/releases/tag/v0.8.6
This update for cni, cni-plugins, conmon, fuse-overlayfs, podman fixes the following issues: podman was updated to 1.8.0: - CVE-2019-18466: Fixed a bug where podman cp would improperly copy files on the host when copying a symlink in the container that included a glob operator (#3829 bsc#1155217) - The name of the cni-bridge in the default config changed from 'cni0' to 'podman-cni0' with podman-1.6.0. Add a %trigger to rename the bridge in the system to the new default if it exists. The trigger is only excuted when updating podman-cni-config from something older than 1.6.0. This is mainly needed for SLE where we're updating
Check your installed stack and versions against the current vulnerability feeds.