[secdir] Secdir review of draft-ietf-netmod-yang-12

Alan DeKok <aland@deployingradius.com> Wed, 28 April 2010 13:38 UTC

Return-Path: <aland@deployingradius.com>
X-Original-To: secdir@core3.amsl.com
Delivered-To: secdir@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id A913C28C14F; Wed, 28 Apr 2010 06:38:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.554
X-Spam-Status: No, score=0.554 tagged_above=-999 required=5 tests=[AWL=0.553, BAYES_50=0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id Y40PzjLv4NFT; Wed, 28 Apr 2010 06:38:26 -0700 (PDT)
Received: from liberty.deployingradius.com (liberty.deployingradius.com []) by core3.amsl.com (Postfix) with ESMTP id 6F6423A6BFF; Wed, 28 Apr 2010 06:36:53 -0700 (PDT)
Message-ID: <4BD839E7.4040200@deployingradius.com>
Date: Wed, 28 Apr 2010 15:36:39 +0200
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird (Macintosh/20100228)
MIME-Version: 1.0
To: secdir@ietf.org, IESG IESG <iesg@ietf.org>, draft-ietf-netmod-yang@tools.ietf.org
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: [secdir] Secdir review of draft-ietf-netmod-yang-12
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 28 Apr 2010 13:38:27 -0000

  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.

  The document defines a language used to read and write descriptions of
management information.  It is not intended to be used within an "on the
wire" internet protocol.  As such, the usual "on the wire" security
issues do not apply.

  The "Security Considerations" looks OK.  I would suggest adding a
caution about reading data from untrusted sources.  Document readers
have a long history of being attacked by malformed documents.


YANG parsers need to be robust with respect to malformed documents.
Reading malformed documents from unknown or untrusted sources could
result in an attacker gaining privileges of the user running the YANG
parser.  In an extreme situation, the entire machine could be compromised.

  Alan DeKok.