Incus vulnerable to DoS through antispoofing nftables firewall rule bypass on bridge networks with ACLs
lxc incus
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/lxc/incus/v6 Go |
|
|
| github.com/lxc/incus Go |
| No fix yet |
lxc incus
| Product | Affected | Fixed in |
|---|---|---|
| github.com/lxc/incus/v6 Go |
|
|
| github.com/lxc/incus Go |
| No fix yet |
Incus is a system container and virtual machine manager. When using an ACL on a device connected to a bridge, Incus version 6.12 and 6.13 generates nftables rules for local services (DHCP, DNS...) that partially bypass security options `security.mac_filtering`, `security.ipv4_filtering` and `security.ipv6_filtering`. This can lead to DHCP pool exhaustion and opens the door for other attacks. A patch is available at commit 2516fb19ad8428454cb4edfe70c0a5f0dc1da214.
From the CVE record · GitHub_M
Incus 6.12 and 6.13 generate nftables rules for local services that partially bypass MAC and IP filtering when an ACL is used on a device connected to a bridge. This can allow DHCP pool exhaustion and other attacks. The input does not specify whether authentication or user interaction is required.
Engineers running Incus 6.12 or 6.13 with an ACL on a bridge-connected device should check their deployments; the Go package github.com/lxc/incus/v6 is fixed in 6.14.0, while github.com/lxc/incus has no fixed version listed.