pf incorrectly matches different ICMPv6 states in the state table
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in p5, p9 and p3.
In ICMPv6 Neighbor Discovery (ND), the ID is always 0. When pf is configured to allow ND and block incoming Echo Requests, a crafted Echo Request packet after a Neighbor Solicitation (NS) can trigger an Echo Reply. The packet has to come from the same host as the NS and have a zero as identifier to match the state created by the Neighbor Discovery and allow replies to be generated. ICMPv6 packets with identifier value of zero bypass firewall rules written on the assumption that the incoming packets are going to create a state in the state table.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| FreeBSD | >=13.3-RELEASE <p5, >=14.0-RELEASE <p9, >=14.1-RELEASE <p3 | p5, p9, p3 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket