CVE Vulnerabilities

CVE-2017-2315

Missing Release of Resource after Effective Lifetime

Published: Apr 24, 2017 | Modified: Oct 03, 2019
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
7.8 HIGH
AV:N/AC:L/Au:N/C:N/I:N/A:C
RedHat/V2
RedHat/V3
Ubuntu

On Juniper Networks EX Series Ethernet Switches running affected Junos OS versions, a vulnerability in IPv6 processing has been discovered that may allow a specially crafted IPv6 Neighbor Discovery (ND) packet destined to an EX Series Ethernet Switch to cause a slow memory leak. A malicious network-based packet flood of these crafted IPv6 NDP packets may eventually lead to resource exhaustion and a denial of service. The affected Junos OS versions are: 12.3 prior to 12.3R12-S4, 12.3R13; 13.3 prior to 13.3R10; 14.1 prior to 14.1R8-S3, 14.1R9; 14.1X53 prior ro 14.1X53-D12, 14.1X53-D40; 14.1X55 prior to 14.1X55-D35; 14.2 prior to 14.2R6-S4, 14.2R7-S6, 14.2R8; 15.1 prior to 15.1R5; 16.1 before 16.1R3; 16.2 before 16.2R1-S3, 16.2R2. 17.1R1 and all subsequent releases have a resolution for this vulnerability.

Weakness

The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.

Affected Software

Name Vendor Start Version End Version
Junos Juniper 12.3-r1 (including) 12.3-r1 (including)
Junos Juniper 12.3-r10 (including) 12.3-r10 (including)
Junos Juniper 12.3-r11 (including) 12.3-r11 (including)
Junos Juniper 12.3-r12 (including) 12.3-r12 (including)
Junos Juniper 12.3-r13 (including) 12.3-r13 (including)
Junos Juniper 12.3-r2 (including) 12.3-r2 (including)
Junos Juniper 12.3-r3 (including) 12.3-r3 (including)
Junos Juniper 12.3-r4 (including) 12.3-r4 (including)
Junos Juniper 12.3-r5 (including) 12.3-r5 (including)
Junos Juniper 12.3-r6 (including) 12.3-r6 (including)
Junos Juniper 12.3-r7 (including) 12.3-r7 (including)
Junos Juniper 12.3-r8 (including) 12.3-r8 (including)
Junos Juniper 12.3-r9 (including) 12.3-r9 (including)
Junos Juniper 13.3-r1 (including) 13.3-r1 (including)
Junos Juniper 13.3-r2 (including) 13.3-r2 (including)
Junos Juniper 13.3-r3 (including) 13.3-r3 (including)
Junos Juniper 13.3-r4 (including) 13.3-r4 (including)
Junos Juniper 13.3-r5 (including) 13.3-r5 (including)
Junos Juniper 13.3-r6 (including) 13.3-r6 (including)
Junos Juniper 13.3-r7 (including) 13.3-r7 (including)
Junos Juniper 13.3-r8 (including) 13.3-r8 (including)
Junos Juniper 13.3-r9 (including) 13.3-r9 (including)
Junos Juniper 14.1-r1 (including) 14.1-r1 (including)
Junos Juniper 14.1-r2 (including) 14.1-r2 (including)
Junos Juniper 14.1-r3 (including) 14.1-r3 (including)
Junos Juniper 14.1-r4 (including) 14.1-r4 (including)
Junos Juniper 14.1-r5 (including) 14.1-r5 (including)
Junos Juniper 14.1-r6 (including) 14.1-r6 (including)
Junos Juniper 14.1-r7 (including) 14.1-r7 (including)
Junos Juniper 14.1-r9 (including) 14.1-r9 (including)
Junos Juniper 14.1x53-d10 (including) 14.1x53-d10 (including)
Junos Juniper 14.1x53-d40 (including) 14.1x53-d40 (including)
Junos Juniper 14.1x55-d35 (including) 14.1x55-d35 (including)
Junos Juniper 14.2-r1 (including) 14.2-r1 (including)
Junos Juniper 14.2-r2 (including) 14.2-r2 (including)
Junos Juniper 14.2-r3 (including) 14.2-r3 (including)
Junos Juniper 14.2-r4 (including) 14.2-r4 (including)
Junos Juniper 14.2-r5 (including) 14.2-r5 (including)
Junos Juniper 14.2-r7 (including) 14.2-r7 (including)
Junos Juniper 14.2-r8 (including) 14.2-r8 (including)
Junos Juniper 15.1-r1 (including) 15.1-r1 (including)
Junos Juniper 15.1-r2 (including) 15.1-r2 (including)
Junos Juniper 15.1-r3 (including) 15.1-r3 (including)
Junos Juniper 15.1-r4 (including) 15.1-r4 (including)
Junos Juniper 16.1-r1 (including) 16.1-r1 (including)
Junos Juniper 16.2-r2 (including) 16.2-r2 (including)
Junos Juniper 17.1-r1 (including) 17.1-r1 (including)

Potential Mitigations

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • For example, languages such as Java, Ruby, and Lisp perform automatic garbage collection that releases memory for objects that have been deallocated.
  • Use resource-limiting settings provided by the operating system or environment. For example, when managing system resources in POSIX, setrlimit() can be used to set limits for certain types of resources, and getrlimit() can determine how many resources are available. However, these functions are not available on all operating systems.
  • When the current levels get close to the maximum that is defined for the application (see CWE-770), then limit the allocation of further resources to privileged users; alternately, begin releasing resources for less-privileged users. While this mitigation may protect the system from attack, it will not necessarily stop attackers from adversely impacting other users.
  • Ensure that the application performs the appropriate error checks and error handling in case resources become unavailable (CWE-703).

References