CVE-2017-6707 : Détail

CVE-2017-6707

8.2
/
Haute
OS Command Injection
A03-Injection
0.05%V3
Local
2017-07-05
22h00 +00:00
2017-07-07
07h57 +00:00
CVE.org
NVD
Notifications pour un CVE
Restez informé de toutes modifications pour un CVE spécifique.
Gestion des notifications

Descriptions du CVE

A vulnerability in the CLI command-parsing code of the Cisco StarOS operating system for Cisco ASR 5000 Series 11.0 through 21.0, 5500 Series, and 5700 Series devices and Cisco Virtualized Packet Core (VPC) Software could allow an authenticated, local attacker to break from the StarOS CLI of an affected system and execute arbitrary shell commands as a Linux root user on the system, aka Command Injection. The vulnerability exists because the affected operating system does not sufficiently sanitize commands before inserting them into Linux shell commands. An attacker could exploit this vulnerability by submitting a crafted CLI command for execution in a Linux shell command as a root user. Cisco Bug IDs: CSCvc69329, CSCvc72930.

Informations du CVE

Faiblesses connexes

CWE-ID Nom de la faiblesse Source
CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.

Métriques

Métriques Score Gravité CVSS Vecteur Source
V3.0 8.2 HIGH CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:C/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.

Local

A vulnerability exploitable with Local access means that the vulnerable component is not bound to the network stack, and the attacker's path is via read/write/execute capabilities. In some cases, the attacker may be logged in locally in order to exploit the vulnerability, otherwise, she may rely on User Interaction to execute a malicious file.

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.

High

The attacker is authorized with (i.e. requires) privileges that provide significant (e.g. administrative) control over the vulnerable component that could affect component-wide settings and files.

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.

Changed

An exploited vulnerability can affect resources beyond the authorization privileges intended by the vulnerable component. In this case the vulnerable component and the impacted component are different.

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

 nvd@nist.gov
V2 7.2 AV:L/AC:L/Au:N/C:C/I:C/A:C nvd@nist.gov

EPSS

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

Score EPSS

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.

Percentile EPSS

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

Cisco>>Staros >> Version 11.0_base

Cisco>>Staros >> Version 12.0.0

Cisco>>Staros >> Version 12.1_base

Cisco>>Staros >> Version 12.2\(300\)

Cisco>>Staros >> Version 12.2_base

Cisco>>Staros >> Version 14.0\(600\)

Cisco>>Staros >> Version 14.0.0

Cisco>>Staros >> Version 15.0\(912\)

Cisco>>Staros >> Version 15.0\(935\)

Cisco>>Staros >> Version 15.0\(938\)

Cisco>>Staros >> Version 15.0_base

Cisco>>Staros >> Version 16.0\(900\)

Cisco>>Staros >> Version 16.0.0

Cisco>>Staros >> Version 16.1.0

Cisco>>Staros >> Version 16.1.1

Cisco>>Staros >> Version 16.1.2

Cisco>>Staros >> Version 16.5.0

Cisco>>Staros >> Version 16.5.2

Cisco>>Staros >> Version 17.2.0

Cisco>>Staros >> Version 17.2.0.59184

Cisco>>Staros >> Version 17.3.0

Cisco>>Staros >> Version 17.3.1

Cisco>>Staros >> Version 17.3_base

Cisco>>Staros >> Version 17.7.0

Cisco>>Staros >> Version 18.0.0

Cisco>>Staros >> Version 18.0.0.57828

Cisco>>Staros >> Version 18.0.0.59167

Cisco>>Staros >> Version 18.0.0.59211

Cisco>>Staros >> Version 18.0.l0.59219

Cisco>>Staros >> Version 18.1.0

Cisco>>Staros >> Version 18.1.0.59776

Cisco>>Staros >> Version 18.1.0.59780

Cisco>>Staros >> Version 18.1_base

Cisco>>Staros >> Version 18.3.0

Cisco>>Staros >> Version 18.3_base

Cisco>>Staros >> Version 18.4.0

Cisco>>Staros >> Version 19.0.1

Cisco>>Staros >> Version 19.0.m0.60737

Cisco>>Staros >> Version 19.0.m0.60828

Cisco>>Staros >> Version 19.0.m0.61045

Cisco>>Staros >> Version 19.1.0

Cisco>>Staros >> Version 19.1.0.61559

Cisco>>Staros >> Version 19.2.0

Cisco>>Staros >> Version 19.3.0

Cisco>>Staros >> Version 20.0.0

Cisco>>Staros >> Version 20.0.1.0

Cisco>>Staros >> Version 20.0.1.a0

Cisco>>Staros >> Version 20.0.1.v0

Cisco>>Staros >> Version 20.0.2.3

Cisco>>Staros >> Version 20.0.2.3.65026

Cisco>>Staros >> Version 20.0.2.v1

Cisco>>Staros >> Version 20.0.m0.62842

Cisco>>Staros >> Version 20.0.m0.63229

Cisco>>Staros >> Version 20.0.v0

Cisco>>Staros >> Version 21.0.0

Cisco>>Staros >> Version 21.0_base

Cisco>>Staros >> Version 21.0_m0.64246

Cisco>>Staros >> Version 21.0_m0.64702

Références

http://www.securitytracker.com/id/1038818
Tags : vdb-entry, x_refsource_SECTRACK
http://www.securityfocus.com/bid/99462
Tags : vdb-entry, x_refsource_BID