[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150223231002.GA32636@kria>
Date: Tue, 24 Feb 2015 00:10:02 +0100
From: Sabrina Dubroca <sd@...asysnail.net>
To: Marcelo Ricardo Leitner <mleitner@...hat.com>
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH v2 net] ipv6: addrconf: validate new MTU before applying
it
2015-02-23, 11:17:13 -0300, Marcelo Ricardo Leitner wrote:
> Currently we don't check if the new MTU is valid or not and this allows
> one to configure a smaller than minimum allowed by RFCs or even bigger
> than interface own MTU, which is a problem as it may lead to packet
> drops.
>
> If you have a daemon like NetworkManager running, this may be exploited
> by remote attackers by forging RA packets with an invalid MTU, possibly
> leading to a DoS. (NetworkManager currently only validates for values
> too small, but not for too big ones.)
>
> The fix is just to make sure the new value is valid. That is, between
> IPV6_MIN_MTU and interface's MTU.
>
> Note that similar check is already performed at
> ndisc_router_discovery(), for when kernel itself parses the RA.
>
> Signed-off-by: Marcelo Ricardo Leitner <mleitner@...hat.com>
> ---
>
> Notes:
> Sabrina, please feel free to add your Signed-off-by if you want.
>
> v1->v2, applied Sabrina's notes:
> use proc_dointvec_minmax instead
> protect against all and default cases, which don't have idev
>
> all and default are simply not used, so we are good to simply ignore the
> max values for them. The default value actually comes from interface MTU
> during creation.
>
> net/ipv6/addrconf.c | 17 ++++++++++++++++-
> 1 file changed, 16 insertions(+), 1 deletion(-)
Signed-off-by: Sabrina Dubroca <sd@...asysnail.net>
Thanks Marcelo.
--
Sabrina
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists