In pf packet processing with a 'scrub fragment reassemble' rule, a packet containing multiple IPv6 fragment headers would be reassembled, and then immediately processed. That is, a packet with multiple fragment extension headers would not be recognized as the correct ultimate payload. Instead a packet with multiple IPv6 fragment headers would unexpectedly be interpreted as a fragmented packet, rather than as whatever the real payload is.
As a result, IPv6 fragments may bypass pf firewall rules written on the assumption all fragments have been reassembled and, as a result, be forwarded or processed by the host.
References
Link | Resource |
---|---|
http://www.openwall.com/lists/oss-security/2023/09/08/5 | Mailing List Third Party Advisory |
http://www.openwall.com/lists/oss-security/2023/09/08/6 | Mailing List Third Party Advisory |
http://www.openwall.com/lists/oss-security/2023/09/08/7 | Mailing List Third Party Advisory |
https://security.FreeBSD.org/advisories/FreeBSD-SA-23:10.pf.asc | Vendor Advisory |
https://security.netapp.com/advisory/ntap-20231221-0009/ |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: freebsd
Published: 2023-09-06T19:26:45.833Z
Updated: 2023-09-06T19:26:45.833Z
Reserved: 2023-09-06T17:11:30.349Z
Link: CVE-2023-4809
JSON object: View
NVD Information
Status : Modified
Published: 2023-09-06T20:15:08.080
Modified: 2023-12-21T22:15:15.217
Link: CVE-2023-4809
JSON object: View
Redhat Information
No data.
CWE