CVE-2020-1680 Detail

CVE-2020-1680

Score / Severity

5.3

Medium

EPSS

0.11%V3

Vector

Network

Published

2020-10-16
20h31 +00:00

Modified

2024-09-17
00h55 +00:00

Official links

CVE.org

NVD

Notifications for a CVE

Stay informed of any changes for a specific CVE.

Notifications manage

List of Notifications

Notifications for a CVE

Stay informed of any changes for a specific CVE.

Criteria applied when sending the alert: compared with the last alert sent + differences in CISA, EPSS, CVSS, CWE, Solutions, CPE.

Parameters

You can specify a title that will be retrieved in the alerts that will be sent out.

Specified here a CVE ID as CVE-2025-1234

Planning

Month

Next run calculation

Day

Weekday

Hour

Minute

Creation date

Last execution

Next execution

Functionality requiring a connection

This feature, which allows you to receive alerts, is only active when you are logged into your account.

CVE Descriptions

Junos OS: MX Series: MS-MPC/MIC might crash when processing malformed IPv6 packet in NAT64 configuration.

On Juniper Networks MX Series with MS-MIC or MS-MPC card configured with NAT64 configuration, receipt of a malformed IPv6 packet may crash the MS-PIC component on MS-MIC or MS-MPC. This issue occurs when a multiservice card is translating the malformed IPv6 packet to IPv4 packet. An unauthenticated attacker can continuously send crafted IPv6 packets through the device causing repetitive MS-PIC process crashes, resulting in an extended Denial of Service condition. This issue affects Juniper Networks Junos OS on MX Series: 15.1 versions prior to 15.1R7-S7; 15.1X53 versions prior to 15.1X53-D593; 16.1 versions prior to 16.1R7-S8; 17.2 versions prior to 17.2R3-S4; 17.3 versions prior to 17.3R3-S6; 17.4 versions prior to 17.4R2-S11, 17.4R3; 18.1 versions prior to 18.1R3-S11; 18.2 versions prior to 18.2R3-S6; 18.2X75 versions prior to 18.2X75-D41, 18.2X75-D430, 18.2X75-D53, 18.2X75-D65; 18.3 versions prior to 18.3R2-S4, 18.3R3; 18.4 versions prior to 18.4R2-S5, 18.4R3; 19.1 versions prior to 19.1R2; 19.2 versions prior to 19.2R1-S5, 19.2R2; 19.3 versions prior to 19.3R2.

CVE Solutions

The following software releases have been updated to resolve this specific issue: Junos OS 15.1R7-S7, 15.1X53-D593, 16.1R7-S8, 17.2R3-S4, 17.3R3-S6, 17.4R2-S11, 17.4R3, 18.1R3-S11, 18.2R3-S6, 18.2X75-D41, 18.2X75-D430, 18.2X75-D53, 18.2X75-D65, 18.3R2-S4, 18.3R3, 18.4R2-S5, 18.4R3, 19.1R2, 19.2R1-S5, 19.2R2, 19.3R2, 19.4R1, and all subsequent releases.

CVE Informations

Related Weaknesses

CWE-ID	Weakness Name	Source
CWE-131	Incorrect Calculation of Buffer Size The product does not correctly calculate the size to be used when allocating a buffer, which could lead to a buffer overflow.

Metrics

Metrics	Score	Severity	CVSS Vector	Source
V3.1	5.3	MEDIUM	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L More informations Base: Exploitabilty Metrics The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component. Attack Vector This metric reflects the context by which vulnerability exploitation is possible. Network The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers). Attack Complexity This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability. Low Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component. Privileges Required This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability. None The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack. User Interaction This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component. None The vulnerable system can be exploited without interaction from any user. Base: Scope Metrics The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope. Scope Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs. Unchanged An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority. Base: Impact Metrics The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve. Confidentiality Impact This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability. None There is no loss of confidentiality within the impacted component. Integrity Impact This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. None There is no loss of integrity within the impacted component. Availability Impact This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability. Low Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component. Temporal Metrics The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability. Environmental Metrics These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.
V2	5		AV:N/AC:L/Au:N/C:N/I:N/A:P	[email protected]

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.

EPSS First.org

Products Mentioned

Configuraton 0

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1 (Open CPE detail)