CVE-2018-0029 : Detail

CVE-2018-0029

6.5
/
Medium
0.06%V3
Adjacent
2018-07-11
18h00 +00:00
2024-09-16
19h51 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

Junos OS: Kernel crash (vmcore) during broadcast storm after enabling 'monitor traffic interface fxp0'

While experiencing a broadcast storm, placing the fxp0 interface into promiscuous mode via the 'monitor traffic interface fxp0' can cause the system to crash and restart (vmcore). This issue only affects Junos OS 15.1 and later releases, and affects both single core and multi-core REs. Releases prior to Junos OS 15.1 are unaffected by this vulnerability. Affected releases are Juniper Networks Junos OS: 15.1 versions prior to 15.1F6-S11, 15.1R4-S9, 15.1R6-S6, 15.1R7; 15.1X49 versions prior to 15.1X49-D140; 15.1X53 versions prior to 15.1X53-D59 on EX2300/EX3400; 15.1X53 versions prior to 15.1X53-D67 on QFX10K; 15.1X53 versions prior to 15.1X53-D233 on QFX5200/QFX5110; 15.1X53 versions prior to 15.1X53-D471, 15.1X53-D490 on NFX; 16.1 versions prior to 16.1R3-S8, 16.1R5-S4, 16.1R6-S1, 16.1R7; 16.2 versions prior to 16.2R1-S6, 16.2R2-S5, 16.2R3; 17.1 versions prior to 17.1R1-S7, 17.1R2-S7, 17.1R3; 17.2 versions prior to 17.2R1-S6, 17.2R2-S4, 17.2R3; 17.2X75 versions prior to 17.2X75-D90, 17.2X75-D110; 17.3 versions prior to 17.3R1-S4, 17.3R2; 17.4 versions prior to 17.4R1-S3, 17.4R2.

CVE Solutions

The following software releases have been updated to resolve this specific issue: 15.1F6-S11*, 15.1R4-S9, 15.1R6-S6, 15.1R7, 15.1X49-D140, 15.1X53-D233, 15.1X53-D471, 15.1X53-D490, 15.1X53-D59, 15.1X53-D67, 16.1R3-S8, 16.1R5-S4, 16.1R6-S1, 16.1R7, 16.2R1-S6, 16.2R2-S5, 16.2R3, 17.1R1-S7, 17.1R2-S7, 17.1R3, 17.2R1-S6, 17.2R2-S4, 17.2R3, 17.2X75-D110, 17.2X75-D90, 17.3R1-S4, 17.3R2, 17.4R1-S3, 17.4R2, 18.1R1, 18.1X75-D10, and all subsequent releases. *Future availability

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-400 Uncontrolled Resource Consumption
The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources.

Metrics

Metrics Score Severity CVSS Vector Source
V3.0 5.7 MEDIUM CVSS:3.0/AV:A/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

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.

Adjacent

A vulnerability exploitable with adjacent network access means the vulnerable component is bound to the network stack, however the attack is limited to the same shared physical (e.g. Bluetooth, IEEE 802.11), or logical (e.g. local IP subnet) network, and cannot be performed across an OSI layer 3 boundary (e.g. a router).

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 against 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 to carry out an attack.

User Interaction

This metric captures the requirement for a user, other than the attacker, to participate in the successful compromise of the vulnerable component.

Required

Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator.

Base: Scope Metrics

An important property captured by CVSS v3.0 is the ability for a vulnerability in one software component to impact resources beyond its means, or privileges.

Scope

Formally, Scope refers to the collection of privileges defined by a computing authority (e.g. an application, an operating system, or a sandbox environment) when granting access to computing resources (e.g. files, CPU, memory, etc). These privileges are assigned based on some method of identification and authorization. In some cases, the authorization may be simple or loosely controlled based upon predefined rules or standards. For example, in the case of Ethernet traffic sent to a network switch, the switch accepts traffic that arrives on its ports and is an authority that controls the traffic flow to other switch ports.

Unchanged

An exploited vulnerability can only affect resources managed by the same authority. In this case the vulnerable component and the impacted component are the same.

Base: Impact Metrics

The Impact metrics refer to the properties of the impacted component.

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.

High

There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

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 that one has in the description of a vulnerability.

Environmental Metrics
V3.0 6.5 MEDIUM CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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.

Adjacent

A vulnerability exploitable with adjacent network access means the vulnerable component is bound to the network stack, however the attack is limited to the same shared physical (e.g. Bluetooth, IEEE 802.11), or logical (e.g. local IP subnet) network, and cannot be performed across an OSI layer 3 boundary (e.g. a router).

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 against 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 to carry out an attack.

User Interaction

This metric captures the requirement for a 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

An important property captured by CVSS v3.0 is the ability for a vulnerability in one software component to impact resources beyond its means, or privileges.

Scope

Formally, Scope refers to the collection of privileges defined by a computing authority (e.g. an application, an operating system, or a sandbox environment) when granting access to computing resources (e.g. files, CPU, memory, etc). These privileges are assigned based on some method of identification and authorization. In some cases, the authorization may be simple or loosely controlled based upon predefined rules or standards. For example, in the case of Ethernet traffic sent to a network switch, the switch accepts traffic that arrives on its ports and is an authority that controls the traffic flow to other switch ports.

Unchanged

An exploited vulnerability can only affect resources managed by the same authority. In this case the vulnerable component and the impacted component are the same.

Base: Impact Metrics

The Impact metrics refer to the properties of the impacted component.

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.

High

There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

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 that one has in the description of a vulnerability.

Environmental Metrics

 [email protected]
V2 6.1 AV:A/AC:L/Au:N/C:N/I:N/A:C [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

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Juniper>>Junos >> Version 15.1

Configuraton 0

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Juniper>>Junos >> Version 15.1x49

Configuraton 0

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Ex2300 >> Version -

Juniper>>Ex3400 >> Version -

Configuraton 0

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Qfx5110 >> Version -

Juniper>>Qfx5200 >> Version -

Configuraton 0

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Junos >> Version 15.1x53

Juniper>>Nfx250 >> Version -

Configuraton 0

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Juniper>>Junos >> Version 16.1

Configuraton 0

Juniper>>Junos >> Version 16.2

Juniper>>Junos >> Version 16.2

Juniper>>Junos >> Version 16.2

Juniper>>Junos >> Version 16.2

Configuraton 0

Juniper>>Junos >> Version 17.1

Juniper>>Junos >> Version 17.1

Juniper>>Junos >> Version 17.1

Juniper>>Junos >> Version 17.1

Juniper>>Junos >> Version 17.1

Configuraton 0

Juniper>>Junos >> Version 17.2x75

Juniper>>Junos >> Version 17.2x75

Configuraton 0

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Configuraton 0

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Juniper>>Junos >> Version 17.4

Configuraton 0

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2

References

http://www.securitytracker.com/id/1041319
Tags : vdb-entry, x_refsource_SECTRACK
https://kb.juniper.net/JSA10863
Tags : x_refsource_CONFIRM