CVE-2015-8085 : Detail

CVE-2015-8085

4.9
/
Medium
A02-Cryptographic Failures
0.04%V4
Network
2016-10-03
19h00 +00:00
2016-11-25
18h57 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

Huawei AR routers with software before V200R007C00SPC100; Quidway S9300 routers with software before V200R009C00; S12700 routers with software before V200R008C00SPC500; S9300, Quidway S5300, and S5300 routers with software before V200R007C00; and S5700 routers with software before V200R007C00SPC500 make it easier for remote authenticated administrators to obtain and decrypt passwords by leveraging selection of a reversible encryption algorithm.

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-326 Inadequate Encryption Strength
The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required.

Metrics

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

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.

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.

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.

None

There is no impact to availability within 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

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

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

Huawei>>S9300_firmware >> Version v200r005c00spc300

Huawei>>S9300_firmware >> Version v200r006c00spc500

Huawei>>S9300 >> Version -

Configuraton 0

Huawei>>S12700_firmware >> Version v200r005c00

Huawei>>S12700_firmware >> Version v200r006c00

Huawei>>S12700 >> Version -

Configuraton 0

Huawei>>Quidway_s9300_firmware >> Version v200r001c00spc300

Huawei>>Quidway_s9300_firmware >> Version v200r002c00spc100

Huawei>>Quidway_s9300_firmware >> Version v200r003c00spc500

Huawei>>Quidway_s9300 >> Version -

Configuraton 0

Huawei>>Ar_firmware >> Version v200r001

Huawei>>Ar_firmware >> Version v200r002

Huawei>>Ar_firmware >> Version v200r003

Huawei>>Ar_firmware >> Version v200r005c10

Huawei>>Ar_firmware >> Version v200r005c20

Huawei>>Ar_firmware >> Version v200r005c30

Huawei>>Ar >> Version -

Configuraton 0

Huawei>>Quidway_s5300_firmware >> Version v200r001c00spc300

Huawei>>Quidway_s5300 >> Version -

Configuraton 0

Huawei>>S5700_firmware >> Version v200r001c00

Huawei>>S5700_firmware >> Version v200r002c00

Huawei>>S5700_firmware >> Version v200r003c00

Huawei>>S5700_firmware >> Version v200r005c00

Huawei>>S5700_firmware >> Version v200r006c00

Huawei>>S5700 >> Version -

Configuraton 0

Huawei>>S5300_firmware >> Version v200r002c00

Huawei>>S5300_firmware >> Version v200r005c00spc500

Huawei>>S5300_firmware >> Version v200r006c00spc500

Huawei>>S5300 >> Version -

References

http://www.securityfocus.com/bid/76897
Tags : vdb-entry, x_refsource_BID
The information presented on CVE Find originates from several carefully selected reference sources. CVE data is provided by MITRE Corporation and the National Vulnerability Database (NVD). The Known Exploited Vulnerabilities (KEV) catalog is sourced from the Cybersecurity and Infrastructure Security Agency (CISA), while EPSS scores come from FIRST.org. Additionally, data regarding software weaknesses (CWE) and common attack patterns (CAPEC) is maintained by MITRE Corporation, and information on hardware and software configurations (CPE) is provided by the NVD.