* [PATCH] ipv6: Don't reduce hop limit for an interface
@ 2015-03-25 8:29 D. S. Ljungmark
2015-03-25 15:28 ` Hannes Frederic Sowa
2015-03-25 15:42 ` David Miller
0 siblings, 2 replies; 3+ messages in thread
From: D. S. Ljungmark @ 2015-03-25 8:29 UTC (permalink / raw)
To: netdev
[-- Attachment #1: Type: text/plain, Size: 1749 bytes --]
From 3ae93eb68a06ab2d9c984c6708dbc9e5f3bc8251 Mon Sep 17 00:00:00 2001
From: "D.S. Ljungmark" <ljungmark@modio.se>
Date: Wed, 25 Mar 2015 09:28:15 +0100
Subject: [PATCH] ipv6: Don't reduce hop limit for an interface
A local route may have a lower hop_limit set than global routes do.
RFC 3756, Section 4.2.7, "Parameter Spoofing"
> 1. The attacker includes a Current Hop Limit of one or another small
> number which the attacker knows will cause legitimate packets to
> be dropped before they reach their destination.
> As an example, one possible approach to mitigate this threat is to
> ignore very small hop limits. The nodes could implement a
> configurable minimum hop limit, and ignore attempts to set it below
> said limit.
Signed-off-by: D.S. Ljungmark <ljungmark@modio.se>
---
net/ipv6/ndisc.c | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/net/ipv6/ndisc.c b/net/ipv6/ndisc.c
index 471ed24..14ecdaf 100644
--- a/net/ipv6/ndisc.c
+++ b/net/ipv6/ndisc.c
@@ -1218,7 +1218,14 @@ static void ndisc_router_discovery(struct sk_buff *skb)
if (rt)
rt6_set_expires(rt, jiffies + (HZ * lifetime));
if (ra_msg->icmph.icmp6_hop_limit) {
- in6_dev->cnf.hop_limit = ra_msg->icmph.icmp6_hop_limit;
+ /* Only set hop_limit on the interface if it is higher than
+ * the current hop_limit.
+ */
+ if (in6_dev->cnf.hop_limit < ra_msg->icmph.icmp6_hop_limit) {
+ in6_dev->cnf.hop_limit = ra_msg->icmph.icmp6_hop_limit;
+ } else {
+ ND_PRINTK(2, warn, "RA: Got route advertisement with lower hop_limit than current\n");
+ }
if (rt)
dst_metric_set(&rt->dst, RTAX_HOPLIMIT,
ra_msg->icmph.icmp6_hop_limit);
--
2.1.0
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] ipv6: Don't reduce hop limit for an interface
2015-03-25 8:29 [PATCH] ipv6: Don't reduce hop limit for an interface D. S. Ljungmark
@ 2015-03-25 15:28 ` Hannes Frederic Sowa
2015-03-25 15:42 ` David Miller
1 sibling, 0 replies; 3+ messages in thread
From: Hannes Frederic Sowa @ 2015-03-25 15:28 UTC (permalink / raw)
To: ljungmark, netdev
On Wed, Mar 25, 2015, at 09:29, D. S. Ljungmark wrote:
> From 3ae93eb68a06ab2d9c984c6708dbc9e5f3bc8251 Mon Sep 17 00:00:00 2001
> From: "D.S. Ljungmark" <ljungmark@modio.se>
> Date: Wed, 25 Mar 2015 09:28:15 +0100
> Subject: [PATCH] ipv6: Don't reduce hop limit for an interface
>
> A local route may have a lower hop_limit set than global routes do.
>
> RFC 3756, Section 4.2.7, "Parameter Spoofing"
>
> > 1. The attacker includes a Current Hop Limit of one or another small
> > number which the attacker knows will cause legitimate packets to
> > be dropped before they reach their destination.
>
> > As an example, one possible approach to mitigate this threat is to
> > ignore very small hop limits. The nodes could implement a
> > configurable minimum hop limit, and ignore attempts to set it below
> > said limit.
>
> Signed-off-by: D.S. Ljungmark <ljungmark@modio.se>
> ---
> net/ipv6/ndisc.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/net/ipv6/ndisc.c b/net/ipv6/ndisc.c
> index 471ed24..14ecdaf 100644
> --- a/net/ipv6/ndisc.c
> +++ b/net/ipv6/ndisc.c
> @@ -1218,7 +1218,14 @@ static void ndisc_router_discovery(struct sk_buff
> *skb)
> if (rt)
> rt6_set_expires(rt, jiffies + (HZ * lifetime));
> if (ra_msg->icmph.icmp6_hop_limit) {
> - in6_dev->cnf.hop_limit = ra_msg->icmph.icmp6_hop_limit;
> + /* Only set hop_limit on the interface if it is higher
> than
> + * the current hop_limit.
> + */
> + if (in6_dev->cnf.hop_limit <
> ra_msg->icmph.icmp6_hop_limit) {
> + in6_dev->cnf.hop_limit =
> ra_msg->icmph.icmp6_hop_limit;
> + } else {
> + ND_PRINTK(2, warn, "RA: Got route advertisement
> with lower hop_limit than current\n");
> + }
I think this is the simplest solution to this problem and solves the
problem by default, thanks!
Acked-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH] ipv6: Don't reduce hop limit for an interface
2015-03-25 8:29 [PATCH] ipv6: Don't reduce hop limit for an interface D. S. Ljungmark
2015-03-25 15:28 ` Hannes Frederic Sowa
@ 2015-03-25 15:42 ` David Miller
1 sibling, 0 replies; 3+ messages in thread
From: David Miller @ 2015-03-25 15:42 UTC (permalink / raw)
To: ljungmark, spider; +Cc: netdev
From: "D. S. Ljungmark" <spider@takeit.se>
Date: Wed, 25 Mar 2015 09:29:01 +0100
> From 3ae93eb68a06ab2d9c984c6708dbc9e5f3bc8251 Mon Sep 17 00:00:00 2001
> From: "D.S. Ljungmark" <ljungmark@modio.se>
> Date: Wed, 25 Mar 2015 09:28:15 +0100
> Subject: [PATCH] ipv6: Don't reduce hop limit for an interface
>
> A local route may have a lower hop_limit set than global routes do.
>
> RFC 3756, Section 4.2.7, "Parameter Spoofing"
>
>> 1. The attacker includes a Current Hop Limit of one or another small
>> number which the attacker knows will cause legitimate packets to
>> be dropped before they reach their destination.
>
>> As an example, one possible approach to mitigate this threat is to
>> ignore very small hop limits. The nodes could implement a
>> configurable minimum hop limit, and ignore attempts to set it below
>> said limit.
>
> Signed-off-by: D.S. Ljungmark <ljungmark@modio.se>
Applied and queued up for -stable.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-03-25 15:42 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-03-25 8:29 [PATCH] ipv6: Don't reduce hop limit for an interface D. S. Ljungmark
2015-03-25 15:28 ` Hannes Frederic Sowa
2015-03-25 15:42 ` David Miller
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).