cve.bz

CVE-2016-10142 ietf ipv6: Code

8.6 highEPSS 2.8%

High (8.6) in ietf ipv6. EPSS 2.8% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.0

8.6 high
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
EPSS
2.8% (unchanged from 2.8% a week ago; 2.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 87th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-17 Code deprecated by MITRE
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2016-10142 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2016-10142?via=ask-ai-copy and https://cve.bz/cve/CVE-2016-10142?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2016-10142 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu14.04:LTSlinux3.13.0-51.84UBUNTU-CVE-2016-10142
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-azure and 1 moreno fix listedUBUNTU-CVE-2016-10142
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 2 moreno fix listedUBUNTU-CVE-2016-10142
Ubuntu22.04:LTSlinux-riscv, linux-realtime, linux-intel-iot-realtimeno fix listedUBUNTU-CVE-2016-10142
Ubuntu24.04:LTSlinux-riscv, linux-gcp-6.11, linux-hwe-6.11 and 4 moreno fix listedUBUNTU-CVE-2016-10142
UbuntuPro:20.04:LTSlinux-azure-fde-5.15no fix listedUBUNTU-CVE-2016-10142
Red Hatenterprise_linux:6::client, enterprise_linux:6::computenode, enterprise_linux:6::workstationperf, kernel, kernel-doc and 13 more0:2.6.32-696.el6RHSA-2017:0817
Red Hatenterprise_linux:6::serverperf, kernel, kernel-doc and 19 more0:2.6.32-696.el6RHSA-2017:0817

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu · Red Hat.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This issue affects the Linux kernel shipping with Red Hat Enterprise Linux 7 and MRG-2 prior to 2.6.32-440. Versions after this release have the solution applied.

This issue also affects the Linux kernel packages as shipped with Red Hat Enterprise Linux 6. Future updates for the respective releases may address the issue.

This issue does not not affect Red Hat Enterprise Linux 5.

This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates of Red Hat Enterprise Linux 5. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 6kernel-0:2.6.32-696.el6Fixed 2017-03-21RHSA-2017:0817
Red Hat Enterprise Linux 4kernelNot affected
Red Hat Enterprise Linux 5kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise MRG 2realtime-kernelNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2016-10142.

References

Check your stackJSON