製品・ソフトウェアに関する情報
IPv6 プロトコル仕様の ICMP Packet Too Big メッセージにおけるフラグメンテーションの使用を誘発される脆弱性
Title IPv6 プロトコル仕様の ICMP Packet Too Big メッセージにおけるフラグメンテーションの使用を誘発される脆弱性
Summary

IPv6 プロトコル仕様の ICMP Packet Too Big (PTB) メッセージには、フラグメンテーションの使用を誘発され、その後、レガシー IPv6 ノードに対して任意の種類のフラグメンテーションベースの攻撃を実行される脆弱性が存在します。

Possible impacts 攻撃者により、サービス運用妨害 (DoS) 状態にされる可能性があります。
Solution

ベンダより正式な対策が公開されています。ベンダ情報を参照して適切な対策を実施してください。

Publication Date Sept. 12, 2016, midnight
Registration Date Jan. 30, 2017, 3:45 p.m.
Last Update Jan. 30, 2017, 3:45 p.m.
CVSS3.0 : 重要
Score 8.6
Vector CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
CVSS2.0 : 警告
Score 5
Vector AV:N/AC:L/Au:N/C:N/I:N/A:P
Affected System
インターネット技術タスクフォース (IETF)
IPv6 
CVE (情報セキュリティ 共通脆弱性識別子)
CWE (共通脆弱性タイプ一覧)
ベンダー情報
Change Log
No Changed Details Date of change
0 [2017年01月30日]
  掲載
Feb. 17, 2018, 10:37 a.m.

NVD Vulnerability Information
CVE-2016-10142
Summary

An issue was discovered in the IPv6 protocol specification, related to ICMP Packet Too Big (PTB) messages. (The scope of this CVE is all affected IPv6 implementations from all vendors.) The security implications of IP fragmentation have been discussed at length in [RFC6274] and [RFC7739]. An attacker can leverage the generation of IPv6 atomic fragments to trigger the use of fragmentation in an arbitrary IPv6 flow (in scenarios in which actual fragmentation of packets is not needed) and can subsequently perform any type of fragmentation-based attack against legacy IPv6 nodes that do not implement [RFC6946]. That is, employing fragmentation where not actually needed allows for fragmentation-based attack vectors to be employed, unnecessarily. We note that, unfortunately, even nodes that already implement [RFC6946] can be subject to DoS attacks as a result of the generation of IPv6 atomic fragments. Let us assume that Host A is communicating with Host B and that, as a result of the widespread dropping of IPv6 packets that contain extension headers (including fragmentation) [RFC7872], some intermediate node filters fragments between Host B and Host A. If an attacker sends a forged ICMPv6 PTB error message to Host B, reporting an MTU smaller than 1280, this will trigger the generation of IPv6 atomic fragments from that moment on (as required by [RFC2460]). When Host B starts sending IPv6 atomic fragments (in response to the received ICMPv6 PTB error message), these packets will be dropped, since we previously noted that IPv6 packets with extension headers were being dropped between Host B and Host A. Thus, this situation will result in a DoS scenario. Another possible scenario is that in which two BGP peers are employing IPv6 transport and they implement Access Control Lists (ACLs) to drop IPv6 fragments (to avoid control-plane attacks). If the aforementioned BGP peers drop IPv6 fragments but still honor received ICMPv6 PTB error messages, an attacker could easily attack the corresponding peering session by simply sending an ICMPv6 PTB message with a reported MTU smaller than 1280 bytes. Once the attack packet has been sent, the aforementioned routers will themselves be the ones dropping their own traffic.

Publication Date Jan. 14, 2017, 4:59 p.m.
Registration Date Jan. 26, 2021, 2:05 p.m.
Last Update Nov. 21, 2024, 11:43 a.m.
Affected software configurations
Configuration1 or higher or less more than less than
cpe:2.3:a:ietf:ipv6:-:*:*:*:*:*:*:*
Related information, measures and tools
Common Vulnerabilities List