Date: Wed, 25 Jan 2006 10:14:30 -0500 (EST) From: "Brian A. Seklecki" <lavalamp@spiritual-machines.org> To: freebsd-questions@freebsd.org Subject: Re: [FreeBSD-Announce] FreeBSD Security Advisory FreeBSD-SA-06:07.pf Message-ID: <20060125095918.K37425@arbitor.digitalfreaks.org> In-Reply-To: <200601251013.k0PADhKN059136@freefall.freebsd.org> References: <200601251013.k0PADhKN059136@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> III. Impact > > By sending carefully crafted sequence of IP packet fragments, a remote > attacker can cause a system running pf with a ruleset containing a > 'scrub fragment crop' or 'scrub fragment drop-ovl' rule to crash. > > IV. Workaround > > Do not use 'scrub fragment crop' or 'scrub fragment drop-ovl' rules > on systems running pf. In most cases, such rules can be replaced by > 'scrub fragment reassemble' rules; see the pf.conf(5) manual page for All: Just to clarify on the syntax, since it's not actually mentioned in pf.conf(5): Per the PF FAQ, a rule: "scrub in all" or "scrub all" Implies "scrub in all fragment reassemble" as a default argument/flags to "scrub" when not are specified, and none of the other scrubbing options (no-df, random-id, etc.). This per observation of "pfctl -s all": $ sudo grep -i scrub /etc/pf.conf scrub in all $ sudo pfctl -s all | grep -i scrub scrub in all fragment reassemble Correct? To the credit of the FAQ Author, it does state "This is the default behavior when no fragment option is specified." ... but that still begs the question: "What are the default scrubbing options, other than fragment reassembly, when none are specified?" Might be useful to mention these things in the FAQ and the advisory. TIA, ~lava > more details. > > Systems which do not use pf, or use pf but do not use the aforementioned > rules, are not affected by this issue. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060125095918.K37425>