| 약점 이름 | 출처 | |
|---|---|---|
| Improper Authentication When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. |
| 메트릭 | 점수 | 심각도 | CVSS 벡터 | 출처 |
|---|---|---|---|---|
| V3.0 | 4.6 | MEDIUM |
CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
추가 정보
Base: Exploitabilty MetricsThe 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. Physical A vulnerability exploitable with Physical access requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief (e.g. evil maid attack [1]) or persistent. An example of such an attack is a cold boot attack which allows an attacker to access to disk encryption keys after gaining physical access to the system, or peripheral attacks such as Firewire/USB Direct Memory Access attacks. 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 MetricsAn 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 MetricsThe 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. 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. None There is no impact to availability within the impacted component. Temporal MetricsThe 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 | 2.1 | AV:L/AC:L/Au:N/C:N/I:P/A:N | nvd@nist.gov |
Huawei>>Berlin-l21_firmware >> Version berlin-l21c10b130
Huawei>>Berlin-l21_firmware >> Version berlin-l21c185b133
Huawei>>Berlin-l21 >> Version -
Huawei>>Berlin-l21hn_firmware >> Version berlin-l21hnc10b131
Huawei>>Berlin-l21hn_firmware >> Version berlin-l21hnc185b140
Huawei>>Berlin-l21hn_firmware >> Version berlin-l21hnc432b151
Huawei>>Berlin-l21hn >> Version -
Huawei>>Berlin-l22_firmware >> Version berlin-l22c636b160
Huawei>>Berlin-l22 >> Version -
Huawei>>Berlin-l22hn_firmware >> Version berlin-l22hnc636b130
Huawei>>Berlin-l22hn_firmware >> Version berlin-l22hnc675b150custc675d001
Huawei>>Berlin-l22hn >> Version -
Huawei>>Berlin-l23_firmware >> Version berlin-l23c605b131
Huawei>>Berlin-l23 >> Version -
Huawei>>Berlin-l24hn_firmware >> Version berlin-l24hnc567b110
Huawei>>Berlin-l24hn >> Version -
Huawei>>Frd-l02_firmware >> Version frd-l02c432b120
Huawei>>Frd-l02_firmware >> Version frd-l02c635b130
Huawei>>Frd-l02_firmware >> Version frd-l02c675b170custc675d001
Huawei>>Frd-l02 >> Version -
Huawei>>Frd-l04_firmware >> Version frd-l04c567b162
Huawei>>Frd-l04_firmware >> Version frd-l04c605b131
Huawei>>Frd-l04 >> Version -
Huawei>>Frd-l09_firmware >> Version frd-l09c10b130
Huawei>>Frd-l09_firmware >> Version frd-l09c185b130
Huawei>>Frd-l09_firmware >> Version frd-l09c432b131
Huawei>>Frd-l09_firmware >> Version frd-l09c636b130
Huawei>>Frd-l09 >> Version -
Huawei>>Frd-l14_firmware >> Version frd-l14c567b162
Huawei>>Frd-l14 >> Version -
Huawei>>Frd-l19_firmware >> Version frd-l19c10b130
Huawei>>Frd-l19_firmware >> Version frd-l19c432b131
Huawei>>Frd-l19_firmware >> Version frd-l19c636b130
Huawei>>Frd-l19 >> Version -