Re: [secdir] [Netconf] Sec-Dir Review: draft-mm-netconf-time-capability-05.tx

Andy Bierman <andy@yumaworks.com> Wed, 29 July 2015 21:39 UTC

Return-Path: <andy@yumaworks.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4190C1B2DA0 for <secdir@ietfa.amsl.com>; Wed, 29 Jul 2015 14:39:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SdzYoIZK4rX5 for <secdir@ietfa.amsl.com>; Wed, 29 Jul 2015 14:39:52 -0700 (PDT)
Received: from mail-lb0-f173.google.com (mail-lb0-f173.google.com [209.85.217.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5BA11B2D9C for <secdir@ietf.org>; Wed, 29 Jul 2015 14:39:43 -0700 (PDT)
Received: by lbbud7 with SMTP id ud7so11556330lbb.3 for <secdir@ietf.org>; Wed, 29 Jul 2015 14:39:42 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=3SSd7U0mfpRtILoNxpZr4mNRqP4/6E8RAuaYIFoidz0=; b=d92T+Wi2nWhBkVUeXApcbWywUJZCzxQWzn+PmbTr1RN3+f12GZ1lBs74oUX3ZfhQmM LXemDjMLj3apqoUXJ2utLuYEmQTAPmO8mBB/gAh3PD9hFf6UKolR90tTxP4wSPcUCkEr 9AVxfdWmq/6FBAmfuXhQxNLCJF1//SUc5YmYROeBOjjJ8wWjSaerkqijLyMU0ySVupfd pfIn2PIuEPGNsr8dmVMposMNNyNN6j0WUp/DEFotRdPM7hAtUoVxlIy1zXyqj7inde0r 2cMOe3OD2dKTz3krO2+klr3wf+uH1rI2Tmgtp5vO3FZbxA0Gd1PUDT0WNi0p65Lp1nwH KAiQ==
X-Gm-Message-State: ALoCoQl0Ve6bSiYaGrvF/E+tULl3y5S9nhRKSxHWWAIzPw/2fDYilug0vklWwqMFgNAvaFKbDg6O
MIME-Version: 1.0
X-Received: by 10.152.87.205 with SMTP id ba13mr39778711lab.37.1438205982133; Wed, 29 Jul 2015 14:39:42 -0700 (PDT)
Received: by 10.112.200.102 with HTTP; Wed, 29 Jul 2015 14:39:42 -0700 (PDT)
In-Reply-To: <B1C78188-0906-48BC-8E94-52B42442CABF@ogud.com>
References: <B1C78188-0906-48BC-8E94-52B42442CABF@ogud.com>
Date: Wed, 29 Jul 2015 14:39:42 -0700
Message-ID: <CABCOCHRb-9ok6tcBT-h6qMXvo59aGNVdcjmSZNa573uS0nyqig@mail.gmail.com>
From: Andy Bierman <andy@yumaworks.com>
To: Olafur Gudmundsson <ogud@ogud.com>
Content-Type: multipart/alternative; boundary=001a11c3539aade3af051c0a6c2e
Archived-At: <http://mailarchive.ietf.org/arch/msg/secdir/6H-dNOhO1CZ6nJOoAuyVqbgAO18>
Cc: secdir@ietf.org, draft-mm-netconf-time-capability.all@ietf.org, ietf <ietf@ietf.org>, Netconf <netconf@ietf.org>
Subject: Re: [secdir] [Netconf] Sec-Dir Review: draft-mm-netconf-time-capability-05.tx
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Jul 2015 21:39:54 -0000

Hi,

I am curious if this is a security concern.
When an event is scheduled, the ID and its scheduled time
are sent out in a notification to potentially all clients.

notification netconf-scheduled-message {
        leaf schedule-id {
          type string;
          description
            "The ID of the scheduled message.";
        }

        leaf scheduled-time {
          type yang:date-and-time;
          description
            "The time at which the RPC is scheduled to be performed.";
        }

        description
          "Indicates that a scheduled message was received.";

        reference
          "draft-mm-netconf-time-capability
<https://tools.ietf.org/html/draft-mm-netconf-time-capability>:
           Time Capability in NETCONF";
      }



Any client can get these notifications and know the ID (to cancel it)
and the scheduled time.

Is is a security issue that any client can get the schedule-id
and use it to cancel the scheduled RPC?


Andy


On Wed, Jul 29, 2015 at 2:15 PM, Olafur Gudmundsson <ogud@ogud.com> wrote:

> I have reviewed this document as part of the security directorate's
> ongoing effort to review all IETF documents being processed by the
> IESG.  These comments were written primarily for the benefit of the
> security area directors.  Document editors and WG chairs should treat
> these comments just like any other last call comments.
>
> This document is ready for publication
> The document is well written.
>
> The security considerations are clear and accurate. I would like highlight
> one omission though.
> This capability allows an attacker once it has gained access to schedule
> events in the future even
> though attackers access has been detected and revoked.
>
> Olafur
>
> _______________________________________________
> Netconf mailing list
> Netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
>
>