# CVE-2016-10142: Denial of service in n/a > Attackers can cause denial of service by forging ICMPv6 Packet Too Big messages to force unnecessary IPv6 fragmentation, affecting legacy nodes and BGP peers. - **Severity:** High 8.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 14 Jan 2017 - **Updated:** 6 Aug 2024 - **Also known as:** GHSA-4jqq-7wwq-485f, UBUNTU-CVE-2016-10142 ## What is CVE-2016-10142? CVE-2016-10142 is a high-severity denial of service vulnerability in n/a, published on 14 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-17 ## Which versions are affected by CVE-2016-10142? It affects 1 product. Products: Ietf Ipv6. ## How do I fix CVE-2016-10142? Apply the vendor's patch. ## Is CVE-2016-10142 being exploited? There is no known exploitation of CVE-2016-10142 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2007-2242](https://insights.sbomify.com/CVE-2007-2242/): Denial of service in n/a (high 7.8) - [CVE-2025-23018](https://insights.sbomify.com/CVE-2025-23018/): Security feature bypass in IPv6 (medium 5.4) - [CVE-2025-23019](https://insights.sbomify.com/CVE-2025-23019/): Other in IPv6 (medium 5.4) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2016-10142 and fix it if it is affected. What it is: CVE-2016-10142 is a high-severity denial of service vulnerability in n/a, published on 14 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2016-10142 in the wild and no public exploit code. Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2016-10142/ (Markdown: https://insights.sbomify.com/CVE-2016-10142/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2016-10142 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-10142 - OSV: https://osv.dev/vulnerability/CVE-2016-10142 --- From sbomify Insights: https://insights.sbomify.com/CVE-2016-10142/ Summaries are generated and may contain mistakes; the official description above is the record.