CVE-2018-0061 : Détail

CVE-2018-0061

5.3
/
MEDIUM
0.13%V3
Network
2018-10-09 22:00 +00:00
2018-10-11 07:57 +00:00

Alerte pour un CVE

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

Descriptions

Junos OS: Denial of service in telnetd

A denial of service vulnerability in the telnetd service on Junos OS allows remote unauthenticated users to cause high CPU usage which may affect system performance. Affected releases are Juniper Networks Junos OS: 12.1X46 versions prior to 12.1X46-D81 on SRX Series; 12.3 versions prior to 12.3R12-S11; 12.3X48 versions prior to 12.3X48-D80 on SRX Series; 15.1 versions prior to 15.1R7; 15.1X49 versions prior to 15.1X49-D150, 15.1X49-D160 on SRX Series; 15.1X53 versions prior to 15.1X53-D59 on EX2300/EX3400 Series; 15.1X53 versions prior to 15.1X53-D68 on QFX10K Series; 15.1X53 versions prior to 15.1X53-D235 on QFX5200/QFX5110 Series; 15.1X53 versions prior to 15.1X53-D495 on NFX Series; 16.1 versions prior to 16.1R4-S12, 16.1R6-S6, 16.1R7; 16.2 versions prior to 16.2R2-S7, 16.2R3; 17.1 versions prior to 17.1R2-S9, 17.1R3; 17.2 versions prior to 17.2R2-S6, 17.2R3; 17.2X75 versions prior to 17.2X75-D100; 17.3 versions prior to 17.3R2-S4, 17.3R3; 17.4 versions prior to 17.4R1-S5, 17.4R2; 18.2X75 versions prior to 18.2X75-D5.

Solutions

The following software releases have been updated to resolve this specific issue: 12.1X46-D81, 12.3R12-S11, 12.3R13, 12.3X48-D80, 15.1R7, 15.1X49-D150, 15.1X49-D160, 15.1X53-D235, 15.1X53-D495, 15.1X53-D59, 15.1X53-D68, 16.1R4-S12, 16.1R6-S6, 16.1R7, 16.2R2-S7, 16.2R3, 17.1R2-S9, 17.1R3, 17.2R2-S6, 17.2R3, 17.2X75-D100, 17.2X75-D110, 17.3R2-S4, 17.3R3, 17.4R1-S5, 17.4R2, 18.1R1, 18.1R2, 18.2R1, 18.2X75-D5, and all subsequent releases.

Informations

Faiblesses connexes

CWE-ID Nom de la faiblesse 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

Metric Score Sévérité CVSS Vecteur Source
V3.0 5.3 MEDIUM CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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.

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

There is reduced performance or 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 that one has in the description of a vulnerability.

Environmental Metrics

V2 5 AV:N/AC:L/Au:N/C:N/I:N/A:P [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.

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

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

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 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>>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>>Qfx10000 >> 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>>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>>Nfx150 >> Version -

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

Configuraton 0

Juniper>>Junos >> Version 16.2

Juniper>>Junos >> Version 16.2

Configuraton 0

Juniper>>Junos >> Version 17.1

Juniper>>Junos >> Version 17.1

Configuraton 0

Juniper>>Junos >> Version 17.2

Juniper>>Junos >> Version 17.2

Configuraton 0

Juniper>>Junos >> Version 17.2x75

Juniper>>Junos >> Version 17.2x75

Juniper>>Junos >> Version 17.2x75

Configuraton 0

Juniper>>Junos >> Version 17.3

Juniper>>Junos >> Version 17.3

Configuraton 0

Juniper>>Junos >> Version 17.4

Configuraton 0

Juniper>>Junos >> Version 18.2x75

References

https://kb.juniper.net/JSA10896
Tags : x_refsource_CONFIRM
http://www.securitytracker.com/id/1041859
Tags : vdb-entry, x_refsource_SECTRACK
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.