CVE-2022-20934
17h34 +00:00
CVE 설명
CVE 정보
관련 약점
| 약점 이름 | 출처 | |
|---|---|---|
| Improper Neutralization of Special Elements used in a Command The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. |
||
| Improper Neutralization of Special Elements used in an OS Command 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 before it is sent to a downstream component. |
메트릭
| 메트릭 | 점수 | 심각도 | CVSS 벡터 | 출처 |
|---|---|---|---|---|
| V3.1 | 6 | MEDIUM |
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/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. Local The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. 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 when attacking the vulnerable component. Privileges Required This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability. High The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable component allowing access to component-wide settings and files. User Interaction This metric captures the requirement for a human 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 MetricsThe Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope. Scope Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs. Unchanged An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority. Base: Impact MetricsThe Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve. 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 a 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. 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 in the description of a vulnerability. Environmental MetricsThese metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability. |
|
| V3.1 | 6.7 | MEDIUM |
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
추가 정보
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. Local The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. 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 when attacking the vulnerable component. Privileges Required This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability. High The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable component allowing access to component-wide settings and files. User Interaction This metric captures the requirement for a human 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 MetricsThe Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope. Scope Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs. Unchanged An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority. Base: Impact MetricsThe Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve. 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 a 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 a 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 MetricsThe Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability. Environmental MetricsThese metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability. |
nvd@nist.gov |
EPSS
EPSS 점수
EPSS 백분위수
언급된 제품
구성 0
Cisco>>Secure_firewall_threat_defense >> Version 부터 (포함) 6.1.0 까지 (포함) 6.1.0.7
Cisco>>Secure_firewall_threat_defense >> Version 부터 (포함) 6.2.0 까지 (포함) 6.2.0.6
Cisco>>Secure_firewall_threat_defense >> Version 부터 (포함) 6.2.2 까지 (포함) 6.2.2.5
Cisco>>Secure_firewall_threat_defense >> Version 부터 (포함) 6.2.3 까지 (포함) 6.2.3.18
Cisco>>Secure_firewall_threat_defense >> Version 부터 (포함) 6.3.0 까지 (포함) 6.3.0.5
Cisco>>Secure_firewall_threat_defense >> Version 부터 (포함) 6.4.0 까지 (포함) 6.4.0.15
Cisco>>Secure_firewall_threat_defense >> Version 부터 (포함) 6.5.0 까지 (포함) 6.5.0.5
Cisco>>Secure_firewall_threat_defense >> Version 부터 (포함) 6.7.0 까지 (포함) 6.7.0.3
Cisco>>Secure_firewall_threat_defense >> Version 부터 (포함) 7.0.0 까지 (포함) 7.0.4
Cisco>>Secure_firewall_threat_defense >> Version 6.2.1
Cisco>>Secure_firewall_threat_defense >> Version 6.6.0
Cisco>>Secure_firewall_threat_defense >> Version 6.6.0.1
Cisco>>Secure_firewall_threat_defense >> Version 6.6.1
Cisco>>Secure_firewall_threat_defense >> Version 6.6.3
Cisco>>Secure_firewall_threat_defense >> Version 6.6.4
Cisco>>Secure_firewall_threat_defense >> Version 6.6.5
Cisco>>Secure_firewall_threat_defense >> Version 6.6.5.1
Cisco>>Secure_firewall_threat_defense >> Version 6.6.5.2
Cisco>>Secure_firewall_threat_defense >> Version 6.6.7
Cisco>>Secure_firewall_threat_defense >> Version 7.1.0.0
Cisco>>Secure_firewall_threat_defense >> Version 7.1.0.1
Cisco>>Secure_firewall_threat_defense >> Version 7.1.0.2
Cisco>>Secure_firewall_threat_defense >> Version 7.2.0
Cisco>>Secure_firewall_threat_defense >> Version 7.2.0.1
구성 0
Cisco>>Firepower_extensible_operating_system >> Version 1.1.1.147
Cisco>>Firepower_extensible_operating_system >> Version 1.1.1.160
Cisco>>Firepower_extensible_operating_system >> Version 1.1.2.51
Cisco>>Firepower_extensible_operating_system >> Version 1.1.2.178
Cisco>>Firepower_extensible_operating_system >> Version 1.1.3.84
Cisco>>Firepower_extensible_operating_system >> Version 1.1.3.86
Cisco>>Firepower_extensible_operating_system >> Version 1.1.3.97
Cisco>>Firepower_extensible_operating_system >> Version 1.1.4.95
Cisco>>Firepower_extensible_operating_system >> Version 1.1.4.117
Cisco>>Firepower_extensible_operating_system >> Version 1.1.4.140
Cisco>>Firepower_extensible_operating_system >> Version 1.1.4.169
Cisco>>Firepower_extensible_operating_system >> Version 1.1.4.175
Cisco>>Firepower_extensible_operating_system >> Version 1.1.4.178
Cisco>>Firepower_extensible_operating_system >> Version 1.1.4.179
Cisco>>Firepower_extensible_operating_system >> Version 2.0.1.37
Cisco>>Firepower_extensible_operating_system >> Version 2.0.1.68
Cisco>>Firepower_extensible_operating_system >> Version 2.0.1.86
Cisco>>Firepower_extensible_operating_system >> Version 2.0.1.135
Cisco>>Firepower_extensible_operating_system >> Version 2.0.1.141
Cisco>>Firepower_extensible_operating_system >> Version 2.0.1.144
Cisco>>Firepower_extensible_operating_system >> Version 2.0.1.148
Cisco>>Firepower_extensible_operating_system >> Version 2.0.1.149
Cisco>>Firepower_extensible_operating_system >> Version 2.0.1.153
Cisco>>Firepower_extensible_operating_system >> Version 2.0.1.159
Cisco>>Firepower_extensible_operating_system >> Version 2.0.1.188
Cisco>>Firepower_extensible_operating_system >> Version 2.0.1.201
Cisco>>Firepower_extensible_operating_system >> Version 2.0.1.203
Cisco>>Firepower_extensible_operating_system >> Version 2.0.1.204
Cisco>>Firepower_extensible_operating_system >> Version 2.0.1.206
Cisco>>Firepower_extensible_operating_system >> Version 2.1.1.64
Cisco>>Firepower_extensible_operating_system >> Version 2.1.1.73
Cisco>>Firepower_extensible_operating_system >> Version 2.1.1.77
Cisco>>Firepower_extensible_operating_system >> Version 2.1.1.83
Cisco>>Firepower_extensible_operating_system >> Version 2.1.1.85
Cisco>>Firepower_extensible_operating_system >> Version 2.1.1.86
Cisco>>Firepower_extensible_operating_system >> Version 2.1.1.97
Cisco>>Firepower_extensible_operating_system >> Version 2.1.1.106
Cisco>>Firepower_extensible_operating_system >> Version 2.1.1.107
Cisco>>Firepower_extensible_operating_system >> Version 2.1.1.113
Cisco>>Firepower_extensible_operating_system >> Version 2.1.1.115
Cisco>>Firepower_extensible_operating_system >> Version 2.1.1.116
Cisco>>Firepower_extensible_operating_system >> Version 2.2.1.63
Cisco>>Firepower_extensible_operating_system >> Version 2.2.1.66
Cisco>>Firepower_extensible_operating_system >> Version 2.2.1.70
Cisco>>Firepower_extensible_operating_system >> Version 2.2.2.17
Cisco>>Firepower_extensible_operating_system >> Version 2.2.2.19
Cisco>>Firepower_extensible_operating_system >> Version 2.2.2.24
Cisco>>Firepower_extensible_operating_system >> Version 2.2.2.26
Cisco>>Firepower_extensible_operating_system >> Version 2.2.2.28
Cisco>>Firepower_extensible_operating_system >> Version 2.2.2.54
Cisco>>Firepower_extensible_operating_system >> Version 2.2.2.60
Cisco>>Firepower_extensible_operating_system >> Version 2.2.2.71
Cisco>>Firepower_extensible_operating_system >> Version 2.2.2.83
Cisco>>Firepower_extensible_operating_system >> Version 2.2.2.86
Cisco>>Firepower_extensible_operating_system >> Version 2.2.2.91
Cisco>>Firepower_extensible_operating_system >> Version 2.2.2.97
Cisco>>Firepower_extensible_operating_system >> Version 2.2.2.101
Cisco>>Firepower_extensible_operating_system >> Version 2.2.2.137
Cisco>>Firepower_extensible_operating_system >> Version 2.2.2.148
Cisco>>Firepower_extensible_operating_system >> Version 2.2.2.149
Cisco>>Firepower_extensible_operating_system >> Version 2.3.1.56
Cisco>>Firepower_extensible_operating_system >> Version 2.3.1.58
Cisco>>Firepower_extensible_operating_system >> Version 2.3.1.66
Cisco>>Firepower_extensible_operating_system >> Version 2.3.1.73
Cisco>>Firepower_extensible_operating_system >> Version 2.3.1.75
Cisco>>Firepower_extensible_operating_system >> Version 2.3.1.88
Cisco>>Firepower_extensible_operating_system >> Version 2.3.1.91
Cisco>>Firepower_extensible_operating_system >> Version 2.3.1.93
Cisco>>Firepower_extensible_operating_system >> Version 2.3.1.99
Cisco>>Firepower_extensible_operating_system >> Version 2.3.1.110
Cisco>>Firepower_extensible_operating_system >> Version 2.3.1.111
Cisco>>Firepower_extensible_operating_system >> Version 2.3.1.130
Cisco>>Firepower_extensible_operating_system >> Version 2.3.1.144
Cisco>>Firepower_extensible_operating_system >> Version 2.3.1.145
Cisco>>Firepower_extensible_operating_system >> Version 2.3.1.155
Cisco>>Firepower_extensible_operating_system >> Version 2.3.1.166
Cisco>>Firepower_extensible_operating_system >> Version 2.3.1.173
Cisco>>Firepower_extensible_operating_system >> Version 2.3.1.179
Cisco>>Firepower_extensible_operating_system >> Version 2.3.1.180
Cisco>>Firepower_extensible_operating_system >> Version 2.3.1.190
Cisco>>Firepower_extensible_operating_system >> Version 2.3.1.215
Cisco>>Firepower_extensible_operating_system >> Version 2.3.1.216
Cisco>>Firepower_extensible_operating_system >> Version 2.3.1.219
Cisco>>Firepower_extensible_operating_system >> Version 2.4.1.101
Cisco>>Firepower_extensible_operating_system >> Version 2.4.1.214
Cisco>>Firepower_extensible_operating_system >> Version 2.4.1.222
Cisco>>Firepower_extensible_operating_system >> Version 2.4.1.234
Cisco>>Firepower_extensible_operating_system >> Version 2.4.1.238
Cisco>>Firepower_extensible_operating_system >> Version 2.4.1.244
Cisco>>Firepower_extensible_operating_system >> Version 2.4.1.249
Cisco>>Firepower_extensible_operating_system >> Version 2.4.1.252
Cisco>>Firepower_extensible_operating_system >> Version 2.4.1.266
Cisco>>Firepower_extensible_operating_system >> Version 2.4.1.268
Cisco>>Firepower_extensible_operating_system >> Version 2.4.1.273
Cisco>>Firepower_extensible_operating_system >> Version 2.6.1.131
Cisco>>Firepower_extensible_operating_system >> Version 2.6.1.157
Cisco>>Firepower_extensible_operating_system >> Version 2.6.1.166
Cisco>>Firepower_extensible_operating_system >> Version 2.6.1.169
Cisco>>Firepower_extensible_operating_system >> Version 2.6.1.174
Cisco>>Firepower_extensible_operating_system >> Version 2.6.1.187
Cisco>>Firepower_extensible_operating_system >> Version 2.6.1.192
Cisco>>Firepower_extensible_operating_system >> Version 2.6.1.204
Cisco>>Firepower_extensible_operating_system >> Version 2.6.1.214
Cisco>>Firepower_extensible_operating_system >> Version 2.6.1.224
Cisco>>Firepower_extensible_operating_system >> Version 2.6.1.229
Cisco>>Firepower_extensible_operating_system >> Version 2.6.1.230
Cisco>>Firepower_extensible_operating_system >> Version 2.6.1.238
Cisco>>Firepower_extensible_operating_system >> Version 2.6.1.239
Cisco>>Firepower_extensible_operating_system >> Version 2.6.1.254
Cisco>>Firepower_extensible_operating_system >> Version 2.7.1.92
Cisco>>Firepower_extensible_operating_system >> Version 2.7.1.98
Cisco>>Firepower_extensible_operating_system >> Version 2.7.1.106
Cisco>>Firepower_extensible_operating_system >> Version 2.7.1.122
Cisco>>Firepower_extensible_operating_system >> Version 2.7.1.131
Cisco>>Firepower_extensible_operating_system >> Version 2.7.1.143
Cisco>>Firepower_extensible_operating_system >> Version 2.8.1.105
Cisco>>Firepower_extensible_operating_system >> Version 2.8.1.125
Cisco>>Firepower_extensible_operating_system >> Version 2.8.1.139
Cisco>>Firepower_extensible_operating_system >> Version 2.8.1.143
Cisco>>Firepower_extensible_operating_system >> Version 2.8.1.152
Cisco>>Firepower_extensible_operating_system >> Version 2.8.1.162
Cisco>>Firepower_extensible_operating_system >> Version 2.8.1.164
Cisco>>Firepower_extensible_operating_system >> Version 2.8.1.172
Cisco>>Firepower_extensible_operating_system >> Version 2.9.1.131
Cisco>>Firepower_extensible_operating_system >> Version 2.9.1.135
Cisco>>Firepower_extensible_operating_system >> Version 2.9.1.143
Cisco>>Firepower_extensible_operating_system >> Version 2.9.1.150
Cisco>>Firepower_extensible_operating_system >> Version 2.9.1.158
Cisco>>Firepower_extensible_operating_system >> Version 2.10.1.159
Cisco>>Firepower_extensible_operating_system >> Version 2.10.1.166
Cisco>>Firepower_extensible_operating_system >> Version 2.10.1.179
Cisco>>Firepower_extensible_operating_system >> Version 2.11.1.154
