Nom de la faiblesse | Source | |
---|---|---|
Allocation of Resources Without Limits or Throttling The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. |
||
Time-of-check Time-of-use (TOCTOU) Race Condition The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. This can cause the product to perform invalid actions when the resource is in an unexpected state. |
Metric | Score | Sévérité | CVSS Vecteur | Source |
---|---|---|---|---|
V3.1 | 6.1 | MEDIUM |
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:H
More informations
Base: Exploitabilty MetricsThe Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component. Attack VectorThis metric reflects the context by which vulnerability exploitation is possible. Adjacent The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone). Attack ComplexityThis 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 RequiredThis 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 InteractionThis 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. ScopeFormally, 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. Changed An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities. 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 ImpactThis 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 ImpactThis 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 ImpactThis 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. |
Juniper>>Junos_os_evolved >> Version To (excluding) 20.4
Juniper>>Junos_os_evolved >> Version 20.4
Juniper>>Junos_os_evolved >> Version 20.4
Juniper>>Junos_os_evolved >> Version 20.4
Juniper>>Junos_os_evolved >> Version 20.4
Juniper>>Junos_os_evolved >> Version 20.4
Juniper>>Junos_os_evolved >> Version 20.4
Juniper>>Junos_os_evolved >> Version 20.4
Juniper>>Junos_os_evolved >> Version 20.4
Juniper>>Junos_os_evolved >> Version 20.4
Juniper>>Junos_os_evolved >> Version 20.4
Juniper>>Junos_os_evolved >> Version 20.4
Juniper>>Junos_os_evolved >> Version 20.4
Juniper>>Junos_os_evolved >> Version 21.3
Juniper>>Junos_os_evolved >> Version 21.3
Juniper>>Junos_os_evolved >> Version 21.3
Juniper>>Junos_os_evolved >> Version 21.3
Juniper>>Junos_os_evolved >> Version 21.3
Juniper>>Junos_os_evolved >> Version 21.3
Juniper>>Junos_os_evolved >> Version 21.3
Juniper>>Junos_os_evolved >> Version 21.4
Juniper>>Junos_os_evolved >> Version 21.4
Juniper>>Junos_os_evolved >> Version 21.4
Juniper>>Junos_os_evolved >> Version 21.4
Juniper>>Junos_os_evolved >> Version 21.4
Juniper>>Junos_os_evolved >> Version 21.4
Juniper>>Junos_os_evolved >> Version 22.1
Juniper>>Junos_os_evolved >> Version 22.1
Juniper>>Junos_os_evolved >> Version 22.2
Juniper>>Junos_os_evolved >> Version 22.2
Juniper>>Ptx10003 >> Version -