English
Français
Light
Dark
System

CVEFind - Alertes CVE

Restez informé en continue
Créer un compte Ouvrez un compte Simple et Gratuit Se connecter Gérez vos alertes

CVE-2018-0007 : Détail

CVE-2018-0007

9.8
/
CRITICAL
OverflowCommand InjectionCode Injection
A03-Injection
0.17%V3
Network
2018-01-10 21:00 +00:00
2018-01-14 09:57 +00:00
CVE.org
NVD

Alerte pour un CVE

Restez informé de toutes modifications pour un CVE spécifique.
Gestion des alertes

Descriptions

An unauthenticated network-based attacker able to send a maliciously crafted LLDP packet to the local segment, through a local segment broadcast, may be able to cause a Junos device to enter an improper boundary check condition allowing a memory corruption to occur, leading to a denial of service. Further crafted packets may be able to sustain the denial of service condition. Score: 6.5 MEDIUM (CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) Further, if the attacker is authenticated on the target device receiving and processing the malicious LLDP packet, while receiving the crafted packets, the attacker may be able to perform command or arbitrary code injection over the target device thereby elevating their permissions and privileges, and taking control of the device. Score: 7.8 HIGH (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) An unauthenticated network-based attacker able to send a maliciously crafted LLDP packet to one or more local segments, via LLDP proxy / tunneling agents or other LLDP through Layer 3 deployments, through one or more local segment broadcasts, may be able to cause multiple Junos devices to enter an improper boundary check condition allowing a memory corruption to occur, leading to multiple distributed Denials of Services. These Denials of Services attacks may have cascading Denials of Services to adjacent connected devices, impacts network devices, servers, workstations, etc. Further crafted packets may be able to sustain these Denials of Services conditions. Score 6.8 MEDIUM (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:H) Further, if the attacker is authenticated on one or more target devices receiving and processing these malicious LLDP packets, while receiving the crafted packets, the attacker may be able to perform command or arbitrary code injection over multiple target devices thereby elevating their permissions and privileges, and taking control multiple devices. Score: 7.8 HIGH (CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H) Affected releases are Juniper Networks Junos OS: 12.1X46 versions prior to 12.1X46-D71; 12.3 versions prior to 12.3R12-S7; 12.3X48 versions prior to 12.3X48-D55; 14.1 versions prior to 14.1R8-S5, 14.1R9; 14.1X53 versions prior to 14.1X53-D46, 14.1X53-D50, 14.1X53-D107; 14.2 versions prior to 14.2R7-S9, 14.2R8; 15.1 versions prior to 15.1F2-S17, 15.1F5-S8, 15.1F6-S8, 15.1R5-S7, 15.1R7; 15.1X49 versions prior to 15.1X49-D90; 15.1X53 versions prior to 15.1X53-D65; 16.1 versions prior to 16.1R4-S6, 16.1R5; 16.1X65 versions prior to 16.1X65-D45; 16.2 versions prior to 16.2R2; 17.1 versions prior to 17.1R2. No other Juniper Networks products or platforms are affected by this issue.

Informations

Faiblesses connexes

CWE-ID Nom de la faiblesse Source
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
CWE-77 Improper Neutralization of Special Elements used in a Command ('Command Injection')
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
CWE-94 Improper Control of Generation of Code ('Code Injection')
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.

Metrics

Metric Score Sévérité CVSS Vecteur Source
V3.0 9.8 CRITICAL CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.

Network

A vulnerability exploitable with network access means the vulnerable component is bound to the network stack and the attacker's path is through OSI layer 3 (the network layer). Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable one or more network hops away (e.g. across layer 3 boundaries from 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 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.

High

There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

High

There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 10 AV:N/AC:L/Au:N/C:C/I:C/A:C [email protected]

EPSS

EPSS est un modèle de notation qui prédit la probabilité qu'une vulnérabilité soit exploitée.

EPSS Score

Le modèle EPSS produit un score de probabilité compris entre 0 et 1 (0 et 100 %). Plus la note est élevée, plus la probabilité qu'une vulnérabilité soit exploitée est grande.

EPSS Percentile

Le percentile est utilisé pour classer les CVE en fonction de leur score EPSS. Par exemple, une CVE dans le 95e percentile selon son score EPSS est plus susceptible d'être exploitée que 95 % des autres CVE. Ainsi, le percentile sert à comparer le score EPSS d'une CVE par rapport à d'autres CVE.
EPSS First.org

Products Mentioned

Configuraton 0

Juniper>>Junos >> Version 12.1x46

Juniper>>Junos >> Version 12.1x46

Juniper>>Junos >> Version 12.1x46

Juniper>>Junos >> Version 12.1x46

Juniper>>Junos >> Version 12.1x46

Juniper>>Junos >> Version 12.1x46

Juniper>>Junos >> Version 12.1x46

Juniper>>Junos >> Version 12.1x46

Juniper>>Junos >> Version 12.1x46

Juniper>>Junos >> Version 12.1x46

Juniper>>Junos >> Version 12.1x46

Juniper>>Junos >> Version 12.1x46

Juniper>>Junos >> Version 12.1x46

Configuraton 0

Juniper>>Junos >> Version 12.3

Juniper>>Junos >> Version 12.3

Juniper>>Junos >> Version 12.3

Juniper>>Junos >> Version 12.3

Juniper>>Junos >> Version 12.3

Juniper>>Junos >> Version 12.3

Juniper>>Junos >> Version 12.3

Juniper>>Junos >> Version 12.3

Juniper>>Junos >> Version 12.3

Juniper>>Junos >> Version 12.3

Juniper>>Junos >> Version 12.3

Juniper>>Junos >> Version 12.3

Juniper>>Junos >> Version 12.3

Configuraton 0

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48

Juniper>>Junos >> Version 12.3x48

Configuraton 0

Juniper>>Junos >> Version 14.1

Juniper>>Junos >> Version 14.1

Juniper>>Junos >> Version 14.1

Juniper>>Junos >> Version 14.1

Juniper>>Junos >> Version 14.1

Juniper>>Junos >> Version 14.1

Juniper>>Junos >> Version 14.1

Juniper>>Junos >> Version 14.1

Juniper>>Junos >> Version 14.1

Juniper>>Junos >> Version 14.1

Configuraton 0

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Juniper>>Junos >> Version 14.1x53

Configuraton 0

Juniper>>Junos >> Version 14.2

Juniper>>Junos >> Version 14.2

Juniper>>Junos >> Version 14.2

Juniper>>Junos >> Version 14.2

Juniper>>Junos >> Version 14.2

Juniper>>Junos >> Version 14.2

Juniper>>Junos >> Version 14.2

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

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

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

Configuraton 0

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.1x65

Juniper>>Junos >> Version 16.1x65

Juniper>>Junos >> Version 16.1x65

Configuraton 0

Juniper>>Junos >> Version 16.2

Configuraton 0

Juniper>>Junos >> Version 17.1

References

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

Plus d'informations
Cliquez sur le bouton à gauche (OFF), pour autoriser l'inscription de cookie améliorant les fonctionnalités du site. Cliquez sur le bouton à gauche (Tout accepter), pour ne plus autoriser l'inscription de cookie améliorant les fonctionnalités du site.