Faiblesses connexes
CWE-ID |
Nom de la faiblesse |
Source |
CWE-401 |
Missing Release of Memory after Effective Lifetime The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. |
|
Metrics
Metric |
Score |
Sévérité |
CVSS Vecteur |
Source |
V3.1 |
5.3 |
MEDIUM |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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. 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 ComplexityThis metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability. Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component. Privileges RequiredThis metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability. 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. 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. 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 ImpactThis metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability. 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. 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. Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to 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.
|
|
EPSS
EPSS est un modèle de notation qui prédit la probabilité qu'une vulnérabilité soit exploitée.
EPSS Score
Le modèle EPSS produit un score de probabilité compris entre 0 et 1 (0 et 100 %). Plus la note est élevée, plus la probabilité qu'une vulnérabilité soit exploitée est grande.
EPSS Percentile
Le percentile est utilisé pour classer les CVE en fonction de leur score EPSS. Par exemple, une CVE dans le 95e percentile selon son score EPSS est plus susceptible d'être exploitée que 95 % des autres CVE. Ainsi, le percentile sert à comparer le score EPSS d'une CVE par rapport à d'autres CVE.
Products Mentioned
Configuraton 0
Juniper>>Junos >> Version 20.4
Juniper>>Junos >> Version 20.4
Juniper>>Junos >> Version 20.4
Juniper>>Junos >> Version 20.4
Juniper>>Junos >> Version 20.4
Juniper>>Junos >> Version 20.4
Juniper>>Junos >> Version 20.4
Juniper>>Junos >> Version 20.4
Juniper>>Junos >> Version 21.1
Juniper>>Junos >> Version 21.1
Juniper>>Junos >> Version 21.1
Juniper>>Junos >> Version 21.1
Juniper>>Junos >> Version 21.1
Juniper>>Junos >> Version 21.1
Juniper>>Junos >> Version 21.1
Juniper>>Junos >> Version 21.1
Juniper>>Junos >> Version 21.2
Juniper>>Junos >> Version 21.2
Juniper>>Junos >> Version 21.2
Juniper>>Junos >> Version 21.2
Juniper>>Junos >> Version 21.2
Juniper>>Junos >> Version 21.2
Juniper>>Junos >> Version 21.3
Juniper>>Junos >> Version 21.3
Juniper>>Junos >> Version 21.3
Juniper>>Junos >> Version 21.4
Juniper>>Junos >> Version 21.4
Juniper>>Junos >> Version 21.4
Juniper>>Mx10 >> Version -
Juniper>>Mx10000 >> Version -
Juniper>>Mx10003 >> Version -
Juniper>>Mx10008 >> Version -
Juniper>>Mx10016 >> Version -
Juniper>>Mx104 >> Version -
Juniper>>Mx150 >> Version -
Juniper>>Mx2008 >> Version -
Juniper>>Mx2010 >> Version -
Juniper>>Mx2020 >> Version -
Juniper>>Mx204 >> Version -
Juniper>>Mx240 >> Version -
Juniper>>Mx40 >> Version -
Juniper>>Mx480 >> Version -
Juniper>>Mx5 >> Version -
Juniper>>Mx80 >> Version -
Juniper>>Mx960 >> Version -
Juniper>>Srx100 >> Version -
Juniper>>Srx110 >> Version -
Juniper>>Srx1400 >> Version -
Juniper>>Srx1500 >> Version -
Juniper>>Srx210 >> Version -
Juniper>>Srx220 >> Version -
Juniper>>Srx240 >> Version -
Juniper>>Srx240h2 >> Version -
Juniper>>Srx300 >> Version -
Juniper>>Srx320 >> Version -
Juniper>>Srx340 >> Version -
Juniper>>Srx3400 >> Version -
Juniper>>Srx345 >> Version -
Juniper>>Srx3600 >> Version -
Juniper>>Srx380 >> Version -
Juniper>>Srx4000 >> Version -
Juniper>>Srx4100 >> Version -
Juniper>>Srx4200 >> Version -
Juniper>>Srx4600 >> Version -
Juniper>>Srx5000 >> Version -
Juniper>>Srx5400 >> Version -
Juniper>>Srx550 >> Version -
Juniper>>Srx550_hm >> Version -
Juniper>>Srx550m >> Version -
Juniper>>Srx5600 >> Version -
Juniper>>Srx5800 >> Version -
Juniper>>Srx650 >> Version -
References