Re: [secdir] SecDir review of draft-ietf-ospf-prefix-hiding-04

Julien Laganier <julien.ietf@gmail.com> Tue, 17 July 2012 17:22 UTC

Return-Path: <julien.ietf@gmail.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CED2121F863E; Tue, 17 Jul 2012 10:22:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dx5RRnTA6MTg; Tue, 17 Jul 2012 10:22:07 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 9A74221F862F; Tue, 17 Jul 2012 10:22:07 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so1159046pbc.31 for <multiple recipients>; Tue, 17 Jul 2012 10:22:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=+/xKPjJbDGOwuIW50IFtln7lZAktrcZbZtcXhQ1b+rM=; b=j8vLj2EDTIAsRT2Q/6TPWyMGWfADnuWOIrfRbgIJ9geJX5g/t9CilkBIFI97fEKs/7 KyZyLeT7bPoVuB884/CLYr8F2DTAWQg3NoTRaFuZLUs3/MZxyk18QhZQNx5lb0487+xv ovQIVDSUdrb4pXCmkhsvS8YpqD5qE/EaDQ9qhrQCj7I9KWddPmAZUwSXesCYNP+YA1nD d0fhgZ4YpmpN08FZPt8R2pz+b/Tx7XgyTpKTTMm7Vio8WoCrHTF6KEK3MjTnFyzZo+Dm jMN9kQPkrv9hlsRJfDpJU/CKzDUjtDng+pMY0bSZeLVteTnhKy/ludkIQ4Bk/aNtlF+j t7pQ==
MIME-Version: 1.0
Received: by 10.68.193.195 with SMTP id hq3mr451824pbc.30.1342545775339; Tue, 17 Jul 2012 10:22:55 -0700 (PDT)
Received: by 10.68.138.137 with HTTP; Tue, 17 Jul 2012 10:22:55 -0700 (PDT)
In-Reply-To: <C03AAF38AD209F4BB02BC0A34B774CE70BF510@G2W2446.americas.hpqcorp.net>
References: <CAE_dhjvtKqfgJF+vjp1un_672sEZ_gw-6q6N_RsCsYgmrjr36g@mail.gmail.com> <CAE_dhjsgQZoC4_4jJ14JVKrp_ajjOfbbo9iTgp0XsK91mVozDw@mail.gmail.com> <C03AAF38AD209F4BB02BC0A34B774CE70B75F3@G2W2446.americas.hpqcorp.net> <16AA6D76-A64E-4191-B874-B4C84EDB286F@ericsson.com> <C03AAF38AD209F4BB02BC0A34B774CE70BF510@G2W2446.americas.hpqcorp.net>
Date: Tue, 17 Jul 2012 10:22:55 -0700
Message-ID: <CAE_dhjuvs48V1hoFeRya8a3f2Jq-asJXxDwB8L_rVEyqGD9vQA@mail.gmail.com>
From: Julien Laganier <julien.ietf@gmail.com>
To: "Retana, Alvaro" <alvaro.retana@hp.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "secdir@ietf.org" <secdir@ietf.org>, Yi Yang <yiya@cisco.com>, Acee Lindem <acee.lindem@ericsson.com>, "iesg@ietf.org" <iesg@ietf.org>, "draft-ietf-ospf-prefix-hiding.all@tools.ietf.org" <draft-ietf-ospf-prefix-hiding.all@tools.ietf.org>, Abhay Roy <akr@cisco.com>
Subject: Re: [secdir] SecDir review of draft-ietf-ospf-prefix-hiding-04
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Tue, 17 Jul 2012 17:22:09 -0000

Thank you Alvaro. With the new text it is much clearer to me how the
proposal improves security. I have no further concerns.

--julien

On Tue, Jul 10, 2012 at 10:37 AM, Retana, Alvaro <alvaro.retana@hp.com> wrote:
> Julien:
>
> To make sure that your concerns are clarified, I wrote in some new information in the Security Considerations section.   Please see below and let me know if you still have concerns.  We'll publish an update before the deadline on Monday (Jul/9).
>
> Thanks!!
>
> Alvaro.
>
> [Note: the 2 middle paragraphs are new.]
>
> 8. Security Considerations
>
> One motivation for this document is to reduce remote attack vulnerability by hiding transit-only networks.  The result should then be that fewer OSPF core networks will be exposed to un-authorized access.
>
> The mechanisms described above result in reachability information from transit-only networks not being installed in the routers' forwarding tables.  The effect is that even if the address of a transit-only network is known, the forwarding information is not present in the routers to reach the destination.  Also, in some cases the address information is completely omitted from the LSA.
>
> Some information in the LSA (such as the OSPF Router ID) cannot be omitted.  Even though the Router ID is usually taken from an IP address on the router, the configuration can be easily changed.  Note again that having an address doesn't guarantee reachability if the information is hidden from the forwarding tables.
>
> While the steps described in this document are meant to be applied to transit-only networks ONLY, they could be used to hide other networks as well.  It is expected that the same care that users put on the configuration of other routing protocol parameters is used in the configuration of this extension.
>
>
>> -----Original Message-----
>> From: Acee Lindem [mailto:acee.lindem@ericsson.com]
>> Sent: Friday, July 06, 2012 9:33 PM
>> To: Retana, Alvaro
>> Cc: Julien Laganier; Yi Yang; Abhay Roy; secdir@ietf.org; draft-ietf-
>> ospf-prefix-hiding.all@tools.ietf.org; iesg@ietf.org
>> Subject: Re: SecDir review of draft-ietf-ospf-prefix-hiding-04
>>
>> Actually, with this draft, the OSPF LSAs do not necessarily contain any
>> IP addresses - only topology information. The OSPF Router ID certainly
>> doesn't have to be a routable IP address and can be explicitly
>> configured to avoid the default of configured address selection
>> supported by most implementations.
>> Thanks,
>> Acee
>>
>> On Jul 6, 2012, at 4:50 PM, Retana, Alvaro wrote:
>>
>> > Julien:
>> >
>> > Hi!
>> >
>> > [Thanks for forwarding.]
>> >
>> > In short, avoiding installation of the routing information (even if
>> still carried in the LSAs) means that the routers don't have forwarding
>> information to reach a specific transit interface.  IOW, even if you
>> know my IP address you can't send me a packet (if you're more than one
>> hop away).
>> >
>> > We'll expand on the security considerations.
>> >
>> > Thanks!!
>> >
>> > Alvaro.
>> >
>> >> -----Original Message-----
>> >> From: Julien Laganier [mailto:julien.ietf@gmail.com]
>> >> Sent: Friday, July 06, 2012 4:00 PM
>> >> To: Retana, Alvaro
>> >> Subject: Fwd: SecDir review of draft-ietf-ospf-prefix-hiding-04
>> >>
>> >> FYI.
>> >>
>> >>
>> >> ---------- Forwarded message ----------
>> >> From: Julien Laganier <julien.ietf@gmail.com>
>> >> Date: Fri, Jul 6, 2012 at 12:44 PM
>> >> Subject: SecDir review of draft-ietf-ospf-prefix-hiding-04
>> >> To: secdir@ietf.org, draft-ietf-ospf-prefix-
>> hiding.all@tools.ietf.org,
>> >> The IESG <iesg@ietf.org>
>> >>
>> >>
>> >> 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.
>> >>
>> >> Disclaimer: I am no routing or OSPF expert and might be missing
>> >> something obvious...
>> >>
>> >> According to its abstract the draft describes a mechanism that
>> allows
>> >> hiding transit-only networks in OSPF:
>> >>
>> >>  A transit-only network is defined as a network connecting routers
>> >>  only.  In OSPF, transit-only networks are usually configured with
>> >>  routable IP addresses, which are advertised in Link State
>> >>  Advertisements (LSAs) but not needed for data traffic.  In
>> addition,
>> >>  remote attacks can be launched against routers by sending packets
>> to
>> >>  these transit-only networks.  This document presents a mechanism to
>> >>  hide transit-only networks to speed up network convergence and
>> >>  minimize remote attack vulnerability.
>> >>
>> >> While the desire to speed up the network convergence is probably
>> >> obvious and not of concern, I think the document and its security
>> >> considerations section in particular could do a better job at
>> >> explaining what the mechanism achieves in terms of minimizing remote
>> >> attack vulnerability.
>> >>
>> >> As per my understanding, the proposed mechanism essentially remove
>> the
>> >> subnet / netmask information from Link State Advertisements, but
>> these
>> >> still contain the routers' IP addresses.
>> >>
>> >> It is not clear to me how removing the subnet / netmask information
>> >> actually minimizes the risk of remote attacks.
>> >>
>> >> First of all, the type of remote attacks that minimized should be
>> made
>> >> more explicit. What is the target of the remote attacks? Is it any
>> >> address in the subnet? Or the address of a router? If the latter,
>> then
>> >> it is not clear how the mechanism actually improves -- the router's
>> IP
>> >> addresses are still in the LSAs so presumably an attacker can still
>> >> launch remote attacks on these addresses, no? If the former, then it
>> >> is not clear how effective is omission of the subnet in avoiding
>> >> attacks avoid addresses within that subnet -- addresses in the
>> >> (unknown) subnet can still be inferred from addresses of the
>> routers,
>> >> no? Or is it the case that the LSAs containing the IP addresses of
>> the
>> >> routers will not be propagated outside of an area that the attacker
>> >> has no access to?
>> >>
>> >> Expanding the security considerations might help answering these
>> >> questions...
>> >>
>> >> --julien
>