CVE-2016-10142

Assigned byThe organization (CNA) that assigned this CVE ID and published the record, usually the vendor.
MITRE (opens in new tab)
Published
Last modified
NVD status
Modified
CVSS 3.08.6High

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.

Exploitation

Whether attackers are exploiting this vulnerability, and how likely they are to try in the next 30 days.

FIRST Exploit Prediction Scoring System (EPSS)About EPSS (opens in new tab)

FIRST's estimate of the chance attackers try to exploit this vulnerability in the next 30 days.

Probability of exploitationIt predicts attempts, not success, and is updated daily.
2.803%
Compared with other CVEs
At or above 86.78% of scored CVEs
Scored

Affected products

The products and versions with the vulnerability.

Listed by NVD

The CPE names vulnerability scanners match, including products that bundle the affected software.

VendorProductTypeVulnerable versions
ietfipv6Application
  • All versions

Severity

How serious the vulnerability is if exploited, scored from 0 to 10 with the CVSS standard (opens in new tab).

  • 8.6 HighCVSS 3.0 · PrimaryPrimary scores are NVD's own. Secondary scores come from the organization that published the CVE, or from CISA. · Scored by NVD (opens in new tab)
    Attack vectorWhere the attacker has to be. Network is the widest: anywhere on the Internet.
    Network
    Attack complexityWhether the attack depends on conditions the attacker doesn't control.
    Low
    Privileges requiredThe access the attacker needs before attacking.
    None
    User interactionWhether someone other than the attacker has to do something, like open a link.
    None
    ScopeWhether the attack can reach beyond the vulnerable component.
    Changed
    ConfidentialityHow much data the attacker can read.
    None
    IntegrityHow much data the attacker can change.
    None
    AvailabilityHow much the attacker can disrupt the system or service.
    High

    CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:HView in FIRST's calculator (opens in new tab)

  • 5 MediumCVSS 2.0 · PrimaryPrimary scores are NVD's own. Secondary scores come from the organization that published the CVE, or from CISA. · Scored by NVD (opens in new tab)
    Attack vectorWhere the attacker has to be. Network is the widest: anywhere on the Internet.
    Network
    Attack complexityWhether the attack depends on conditions the attacker doesn't control.
    Low
    AuthenticationHow many times the attacker has to sign in.
    None
    ConfidentialityHow much data the attacker can read.
    None
    IntegrityHow much data the attacker can change.
    None
    AvailabilityHow much the attacker can disrupt the system or service.
    Partial

    AV:N/AC:L/Au:N/C:N/I:N/A:PView in NVD's calculator (opens in new tab)

Weaknesses and attack patterns

The type of bug behind the vulnerability, and how attackers exploit that type.

  • DEPRECATED: Code · CWE-17 (opens in new tab)

    This entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.

    Mapping guidance
    Prohibited

References

Advisories, patches, exploits and more about this vulnerability.

This product uses the NVD API but is not endorsed or certified by the NVD (opens in new tab). CVE records from the CVE List (opens in new tab), weakness types from MITRE's CWE (opens in new tab)™ and attack patterns from its CAPEC (opens in new tab)™ are © The MITRE Corporation, used under the CVE (opens in new tab), CWE (opens in new tab) and CAPEC (opens in new tab) terms of use. Known exploited vulnerabilities and SSVC assessments are from CISA. Exploit predictions are from FIRST's EPSS (opens in new tab). About this data