pub enum AvailabilityImpactToTheSubsequentSystem {
None,
Low,
High,
}v4 only.Expand description
Availability Impact to the Subsequent System (SA) - CVSS v4.0 Base Metric Group
Described in CVSS v4.0 Specification: Section 2.2.8
This metric measures the impact to the availability of the impacted system resulting from a successfully exploited vulnerability. While the Confidentiality and Integrity impact metrics apply to the loss of confidentiality or integrity of data (e.g., information, files) used by the system, this metric refers to the loss of availability of the impacted system itself, such as a networked service (e.g., web, database, email). Since availability refers to the accessibility of information resources, attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of a system. The resulting score is greatest when the consequence to the system is highest.
Variants§
None
None (N)
There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Low
Low (L)
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 Subsequent System 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 Subsequent System.
High
High (H)
There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Subsequent System; 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 Subsequent System (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).
Trait Implementations§
Source§impl Clone for AvailabilityImpactToTheSubsequentSystem
impl Clone for AvailabilityImpactToTheSubsequentSystem
Source§fn clone(&self) -> AvailabilityImpactToTheSubsequentSystem
fn clone(&self) -> AvailabilityImpactToTheSubsequentSystem
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read moreSource§impl Ord for AvailabilityImpactToTheSubsequentSystem
impl Ord for AvailabilityImpactToTheSubsequentSystem
Source§fn cmp(&self, other: &AvailabilityImpactToTheSubsequentSystem) -> Ordering
fn cmp(&self, other: &AvailabilityImpactToTheSubsequentSystem) -> Ordering
1.21.0 · Source§fn max(self, other: Self) -> Selfwhere
Self: Sized,
fn max(self, other: Self) -> Selfwhere
Self: Sized,
Source§impl PartialEq for AvailabilityImpactToTheSubsequentSystem
impl PartialEq for AvailabilityImpactToTheSubsequentSystem
Source§fn eq(&self, other: &AvailabilityImpactToTheSubsequentSystem) -> bool
fn eq(&self, other: &AvailabilityImpactToTheSubsequentSystem) -> bool
self and other values to be equal, and is used by ==.