RFC 9267 on Common Implementation Anti-Patterns Related to Domain Name System (DNS) Resource Record (RR) Processing
rfc-editor@rfc-editor.org Thu, 28 July 2022 14:03 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BCDCC157B59 for <ietf-announce@ietfa.amsl.com>; Thu, 28 Jul 2022 07:03:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level:
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jrcy2c7eWiLp for <ietf-announce@ietfa.amsl.com>; Thu, 28 Jul 2022 07:03:16 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BC87DC14CF1E for <ietf-announce@ietf.org>; Thu, 28 Jul 2022 07:03:16 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 83543E5349; Thu, 28 Jul 2022 07:03:16 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9267 on Common Implementation Anti-Patterns Related to Domain Name System (DNS) Resource Record (RR) Processing
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20220728140316.83543E5349@rfcpa.amsl.com>
Date: Thu, 28 Jul 2022 07:03:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/m4XLa4vld0hI07udYJ7BtANJcEg>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jul 2022 14:03:17 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9267
Title: Common Implementation Anti-Patterns Related to
Domain Name System (DNS) Resource Record (RR)
Processing
Author: S. Dashevskyi,
D. dos Santos,
J. Wetzels,
A. Amri
Status: Informational
Stream: Independent
Date: July 2022
Mailbox: stanislav.dashevskyi@forescout.com,
daniel.dossantos@forescout.com,
jos.wetzels@forescout.com,
amine.amri@forescout.com
Pages: 16
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-dashevskyi-dnsrr-antipatterns-06.txt
URL: https://www.rfc-editor.org/info/rfc9267
DOI: 10.17487/RFC9267
This memo describes common vulnerabilities related to Domain Name
System (DNS) resource record (RR) processing as seen in several DNS
client implementations. These vulnerabilities may lead to successful
Denial-of-Service and Remote Code Execution attacks against the
affected software. Where applicable, violations of RFC 1035 are
mentioned.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC