CVE-2018-0294 : Detail

CVE-2018-0294

6.7
/
Medium
A01-Broken Access Control
0.04%V3
Local
2018-06-20
19h00 +00:00
2024-11-29
15h02 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

A vulnerability in the write-erase feature of Cisco FXOS Software and Cisco NX-OS Software could allow an authenticated, local attacker to configure an unauthorized administrator account for an affected device. The vulnerability exists because the affected software does not properly delete sensitive files when certain CLI commands are used to clear the device configuration and reload a device. An attacker could exploit this vulnerability by logging into an affected device as an administrative user and configuring an unauthorized account for the device. The account would not require a password for authentication and would be accessible only via a Secure Shell (SSH) connection to the device. A successful exploit could allow the attacker to configure an unauthorized account that has administrative privileges, does not require a password for authentication, and does not appear in the running configuration or the audit logs for the affected device. This vulnerability affects Firepower 4100 Series Next-Generation Firewalls, Firepower 9300 Security Appliance, Nexus 1000V Series Switches, Nexus 1100 Series Cloud Services Platforms, Nexus 2000 Series Fabric Extenders, Nexus 3500 Platform Switches, Nexus 4000 Series Switches, Nexus 5500 Platform Switches, Nexus 5600 Platform Switches, Nexus 6000 Series Switches, UCS 6100 Series Fabric Interconnects, UCS 6200 Series Fabric Interconnects, UCS 6300 Series Fabric Interconnects. Cisco Bug IDs: CSCvd13993, CSCvd34845, CSCvd34857, CSCvd34862, CSCvd34879, CSCve35753.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-264 Category : Permissions, Privileges, and Access Controls
Weaknesses in this category are related to the management of permissions, privileges, and other security features that are used to perform access control.
CWE Other No informations.

Metrics

Metrics Score Severity CVSS Vector Source
V3.0 6.7 MEDIUM CVSS:3.0/AV:L/AC:L/PR:H/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.

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.

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 7.2 AV:L/AC:L/Au:N/C:C/I:C/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

Cisco>>Nx-os >> Version 7.3\(2\)n1\(0.354\)

Cisco>>Nexus_5000 >> Version -

Cisco>>Nexus_5010 >> Version -

Cisco>>Nexus_5020 >> Version -

Cisco>>Nexus_5548p >> Version -

Cisco>>Nexus_5548up >> Version -

Cisco>>Nexus_5596t >> Version -

Cisco>>Nexus_5596up >> Version -

Cisco>>Nexus_56128p >> Version -

Cisco>>Nexus_5624q >> Version -

Cisco>>Nexus_5648q >> Version -

Cisco>>Nexus_5672up >> Version -

Cisco>>Nexus_5696q >> Version -

Configuraton 0

Cisco>>Nx-os >> Version 5.2\(1\)sv3\(1.10\)

Cisco>>Nexus_1000v >> Version -

Configuraton 0

Cisco>>Nx-os >> Version 8.8\(3.5\)s0

Cisco>>Nexus_92160yc-x >> Version -

Cisco>>Nexus_92304qc >> Version -

Cisco>>Nexus_9236c >> Version -

Cisco>>Nexus_9272q >> Version -

Cisco>>Nexus_93108tc-ex >> Version -

Cisco>>Nexus_93120tx >> Version -

Cisco>>Nexus_93128tx >> Version -

Cisco>>Nexus_93180yc-ex >> Version -

Cisco>>Nexus_9332pq >> Version -

Cisco>>Nexus_9372px >> Version -

Cisco>>Nexus_9372tx >> Version -

Cisco>>Nexus_9396px >> Version -

Cisco>>Nexus_9396tx >> Version -

Cisco>>Nexus_9504 >> Version -

Cisco>>Nexus_9508 >> Version -

Cisco>>Nexus_9516 >> Version -

Cisco>>Nexus_n9k-c9508-fm-r >> Version -

    Cisco>>Nexus_n9k-x9636c-r >> Version -

      Cisco>>Nexus_n9k-x9636q-r >> Version -

        Configuraton 0

        Cisco>>Nx-os >> Version 7.0\(3\)i2\(4a\)

        Cisco>>Nexus_172tq-xl >> Version -

        Cisco>>Nexus_3016 >> Version -

        Cisco>>Nexus_3048 >> Version -

        Cisco>>Nexus_3064-32t >> Version -

        Cisco>>Nexus_3064-t >> Version -

        Cisco>>Nexus_3064-x >> Version -

        Cisco>>Nexus_3100-v >> Version -

        Cisco>>Nexus_31128pq >> Version -

        Cisco>>Nexus_3132c-z >> Version -

        Cisco>>Nexus_3132q >> Version -

        Cisco>>Nexus_3132q-x >> Version -

        Cisco>>Nexus_3132q-xl >> Version -

        Cisco>>Nexus_3164q >> Version -

        Cisco>>Nexus_3172pq >> Version -

        Cisco>>Nexus_3172pq-xl >> Version -

        Cisco>>Nexus_3172tq >> Version -

        Cisco>>Nexus_3172tq-32t >> Version -

        Cisco>>Nexus_3232c >> Version -

        Cisco>>Nexus_3264c-e >> Version -

        Cisco>>Nexus_3264q >> Version -

        Cisco>>Nexus_34180yc >> Version -

        Cisco>>Nexus_3524-x >> Version -

        Cisco>>Nexus_3524-xl >> Version -

        Cisco>>Nexus_3548 >> Version -

        Cisco>>Nexus_3548-x >> Version -

        Cisco>>Nexus_3548-xl >> Version -

        Cisco>>Nexus_3636c-r >> Version -

        Cisco>>Nexus_c36180yc-r >> Version -

          Configuraton 0

          Cisco>>Nx-os >> Version 7.0\(3\)i2\(4a\)

          Cisco>>Ucs_6120xp >> Version -

          Cisco>>Ucs_6140xp >> Version -

          Cisco>>Ucs_6248up >> Version -

          Cisco>>Ucs_6296up >> Version -

          Cisco>>Ucs_6324 >> Version -

          Cisco>>Ucs_6332 >> Version -

          Configuraton 0

          Cisco>>Firepower_extensible_operating_system >> Version From (including) 2.1.1 To (excluding) 2.1.1.86

          Cisco>>Firepower_extensible_operating_system >> Version From (including) 2.2 To (excluding) 2.2.2.17

          Cisco>>Fxos >> Version From (including) 1.1 To (excluding) 2.0.1.159

          Cisco>>Firepower_4110 >> Version -

          Cisco>>Firepower_4120 >> Version -

          Cisco>>Firepower_4140 >> Version -

          Cisco>>Firepower_4150 >> Version -

          Configuraton 0

          Cisco>>Firepower_extensible_operating_system >> Version From (including) 2.1.1 To (excluding) 2.1.1.86

          Cisco>>Firepower_extensible_operating_system >> Version From (including) 2.2 To (excluding) 2.2.2.17

          Cisco>>Fxos >> Version From (including) 1.1 To (excluding) 2.0.1.159

          Cisco>>Firepower_9300_security_appliance >> Version -

          Configuraton 0

          Cisco>>Nx-os >> Version 4.1\(2\)e1\(1a\)

          Cisco>>Nexus_4001 >> Version -

          References

          http://www.securitytracker.com/id/1041169
          Tags : vdb-entry, x_refsource_SECTRACK