lkml.org 
[lkml]   [2016]   [Aug]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Date
    Subject[PATCH 3.16 286/305] tcp: make challenge acks less predictable
    3.16.37-rc1 review patch.  If anyone has any objections, please let me know.

    ------------------

    From: Eric Dumazet <edumazet@google.com>

    commit 75ff39ccc1bd5d3c455b6822ab09e533c551f758 upstream.

    Yue Cao claims that current host rate limiting of challenge ACKS
    (RFC 5961) could leak enough information to allow a patient attacker
    to hijack TCP sessions. He will soon provide details in an academic
    paper.

    This patch increases the default limit from 100 to 1000, and adds
    some randomization so that the attacker can no longer hijack
    sessions without spending a considerable amount of probes.

    Based on initial analysis and patch from Linus.

    Note that we also have per socket rate limiting, so it is tempting
    to remove the host limit in the future.

    v2: randomize the count of challenge acks per second, not the period.

    Fixes: 282f23c6ee34 ("tcp: implement RFC 5961 3.2")
    Reported-by: Yue Cao <ycao009@ucr.edu>
    Signed-off-by: Eric Dumazet <edumazet@google.com>
    Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
    Cc: Yuchung Cheng <ycheng@google.com>
    Cc: Neal Cardwell <ncardwell@google.com>
    Acked-by: Neal Cardwell <ncardwell@google.com>
    Acked-by: Yuchung Cheng <ycheng@google.com>
    Signed-off-by: David S. Miller <davem@davemloft.net>
    [bwh: Backported to 3.16:
    - Adjust context
    - Use ACCESS_ONCE() instead of {READ,WRITE}_ONCE()]
    Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
    ---
    net/ipv4/tcp_input.c | 15 ++++++++++-----
    1 file changed, 10 insertions(+), 5 deletions(-)

    --- a/net/ipv4/tcp_input.c
    +++ b/net/ipv4/tcp_input.c
    @@ -87,7 +87,7 @@ int sysctl_tcp_adv_win_scale __read_most
    EXPORT_SYMBOL(sysctl_tcp_adv_win_scale);

    /* rfc5961 challenge ack rate limiting */
    -int sysctl_tcp_challenge_ack_limit = 100;
    +int sysctl_tcp_challenge_ack_limit = 1000;

    int sysctl_tcp_stdurg __read_mostly;
    int sysctl_tcp_rfc1337 __read_mostly;
    @@ -3285,13 +3285,18 @@ static void tcp_send_challenge_ack(struc
    /* unprotected vars, we dont care of overwrites */
    static u32 challenge_timestamp;
    static unsigned int challenge_count;
    - u32 now = jiffies / HZ;
    + u32 count, now = jiffies / HZ;

    if (now != challenge_timestamp) {
    + u32 half = (sysctl_tcp_challenge_ack_limit + 1) >> 1;
    +
    challenge_timestamp = now;
    - challenge_count = 0;
    + ACCESS_ONCE(challenge_count) =
    + half + prandom_u32_max(sysctl_tcp_challenge_ack_limit);
    }
    - if (++challenge_count <= sysctl_tcp_challenge_ack_limit) {
    + count = ACCESS_ONCE(challenge_count);
    + if (count > 0) {
    + ACCESS_ONCE(challenge_count) = count - 1;
    NET_INC_STATS_BH(sock_net(sk), LINUX_MIB_TCPCHALLENGEACK);
    tcp_send_ack(sk);
    }
    \
     
     \ /
      Last update: 2016-09-17 09:56    [W:4.608 / U:0.108 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site