CVE-2024-20396
16h33 +00:00
Mô tả CVE
Thông tin CVE
Điểm yếu liên quan
| Tên điểm yếu | Nguồn | |
|---|---|---|
| Exposure of Sensitive Information to an Unauthorized Actor The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. |
Số liệu
| Số liệu | Điểm | Mức độ nghiêm trọng | CVSS Vector | Nguồn |
|---|---|---|---|---|
| V3.1 | 5.3 | MEDIUM |
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
Thêm thông tin
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. Network The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers). Attack Complexity This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability. High successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. 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 of the vulnerable system to carry out an attack. 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. Required Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator. 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. 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 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.5 | MEDIUM |
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Thêm thông tin
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. Network The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more 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 when attacking 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 of the vulnerable system to carry out an attack. 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. Required Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator. 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. 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 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
Điểm EPSS
Phân vị EPSS
Sản phẩm được đề cập
Cấu hình 0
Cisco>>Webex_teams >> Version 3.0.13464.0
Cisco>>Webex_teams >> Version 3.0.13538.0
Cisco>>Webex_teams >> Version 3.0.13588.0
Cisco>>Webex_teams >> Version 3.0.14154.0
Cisco>>Webex_teams >> Version 3.0.14234.0
Cisco>>Webex_teams >> Version 3.0.14375.0
Cisco>>Webex_teams >> Version 3.0.14741.0
Cisco>>Webex_teams >> Version 3.0.14866.0
Cisco>>Webex_teams >> Version 3.0.15015.0
Cisco>>Webex_teams >> Version 3.0.15036.0
Cisco>>Webex_teams >> Version 3.0.15092.0
Cisco>>Webex_teams >> Version 3.0.15131.0
Cisco>>Webex_teams >> Version 3.0.15164.0
Cisco>>Webex_teams >> Version 3.0.15221.0
Cisco>>Webex_teams >> Version 3.0.15333.0
Cisco>>Webex_teams >> Version 3.0.15410.0
Cisco>>Webex_teams >> Version 3.0.15485.0
Cisco>>Webex_teams >> Version 3.0.15645.0
Cisco>>Webex_teams >> Version 3.0.15711.0
Cisco>>Webex_teams >> Version 3.0.16040.0
Cisco>>Webex_teams >> Version 3.0.16269.0
Cisco>>Webex_teams >> Version 3.0.16273.0
Cisco>>Webex_teams >> Version 3.0.16285.0
Cisco>>Webex_teams >> Version 42.1.0.21190
Cisco>>Webex_teams >> Version 42.2.0.21338
Cisco>>Webex_teams >> Version 42.2.0.21486
Cisco>>Webex_teams >> Version 42.3.0.21576
Cisco>>Webex_teams >> Version 42.4.1.22032
Cisco>>Webex_teams >> Version 42.5.0.22259
Cisco>>Webex_teams >> Version 42.6.0.22565
Cisco>>Webex_teams >> Version 42.6.0.22645
Cisco>>Webex_teams >> Version 42.7.0.22904
Cisco>>Webex_teams >> Version 42.7.0.23054
Cisco>>Webex_teams >> Version 42.8.0.23214
Cisco>>Webex_teams >> Version 42.8.0.23281
Cisco>>Webex_teams >> Version 42.9.0.23494
Cisco>>Webex_teams >> Version 42.10.0.23814
Cisco>>Webex_teams >> Version 42.11.0.24187
Cisco>>Webex_teams >> Version 42.12.0.24485
Cisco>>Webex_teams >> Version 43.1.0.24716
Cisco>>Webex_teams >> Version 43.2.0.25157
Cisco>>Webex_teams >> Version 43.2.0.25211
Cisco>>Webex_teams >> Version 43.3.0.25468
Cisco>>Webex_teams >> Version 43.4.0.25788
