This CVE record has been analyzed and enriched by NVDAPI.com as an independent party.
Description
A flaw was found in the Open Virtual Network (OVN). Specially crafted UDP packets may bypass egress access control lists (ACLs) in OVN installations configured with a logical switch with DNS records set on it and if the same switch has any egress ACLs configured. This issue can lead to unauthorized access to virtual machines and containers running on the OVN network.
A vulnerability exists in Open Virtual Network (OVN) installations that can lead to unauthorized access to virtual machines and containers. This issue arises because specially crafted UDP packets can bypass egress access control lists (ACLs) on logical switches with DNS records and egress ACLs configured. The vulnerability takes advantage of OVN's optional DNS caching feature, which, when enabled, allows the crafted packets to evade ACL rules that are set to 'to-lport' direction.
Users can upgrade to OVN versions 22.03.8, 24.03.5, or 24.09.2, all of which include patches for this vulnerability. For those using Red Hat Enterprise Linux, the update can be applied through the Red Hat Product Errata advisories RHSA-2025:1084, RHSA-2025:1090, RHSA-2025:1094, and RHSA-2025:1096.
Disable DNS caching in OVN by clearing the "dns_records" column of all logical switches in the northbound database. Use the following command:
$ for s in $(ovn-nbctl list logical_switch | grep uuid | cut -f 2 -d ':') ; do ovn-nbctl clear logical_switch "$s" dns_records ; done
Note: This will increase DNS lookup latency as it will now be performed over the internet instead of using a local cache.
Mitigation:low effort
Adjust ACLs from being evaluated on egress to being evaluated on ingress. ACLs whose "direction" column is set to "to-lport" are evaluated on egress and are vulnerable to being bypassed if OVN's DNS caching is enabled. ACLs whose "direction" column is set to "from-lport" are evaluated on ingress and are not vulnerable to being bypassed if OVN's DNS caching is enabled. An ACL can be evaluated on ingress as long as it does not attempt to match on the "outport" field. Ingress ACLs are capable of matching based on the results of load balancing if "options:apply-after-lb" is set to "true".
Mitigation:low effort
Adjust the topology of the virtual network so that DNS caching and egress ACLs are not on the same logical switch if both are required.
Disable DNS caching in OVN by clearing the "dns_records" column of all logical switches in the northbound database. Use the following command:
$ for s in $(ovn-nbctl list logical_switch | grep uuid | cut -f 2 -d ':') ; do ovn-nbctl clear logical_switch "$s" dns_records ; done
Note: This will increase DNS lookup latency as it will now be performed over the internet instead of using a local cache.
Mitigation:low effort
Adjust ACLs from being evaluated on egress to being evaluated on ingress. ACLs whose "direction" column is set to "to-lport" are evaluated on egress and are vulnerable to being bypassed if OVN's DNS caching is enabled. ACLs whose "direction" column is set to "from-lport" are evaluated on ingress and are not vulnerable to being bypassed if OVN's DNS caching is enabled. An ACL can be evaluated on ingress as long as it does not attempt to match on the "outport" field. Ingress ACLs are capable of matching based on the results of load balancing if "options:apply-after-lb" is set to "true".
Mitigation:low effort
Adjust the topology of the virtual network so that DNS caching and egress ACLs are not on the same logical switch if both are required.