{"_links":{"collection":{"href":"/dashboards/ssvc"},"self":{"href":"/api/v1/ssvc/decision_points_table"}},"data":[{"definition":"Indicates whether another value is near a boundary condition, indicating that special consideration may be needed.","key":"BP","name":"Boundary Proximity","namespace":"basic","values":[{"definition":"The value is not near a boundary condition","key":"NN","name":"Not Near Boundary"},{"definition":"The value is just above a boundary condition","key":"JA","name":"Just Above Boundary"},{"definition":"The value is just below a boundary condition","key":"JB","name":"Just Below Boundary"}],"version":"1.0.0"},{"definition":"A scale for expressing the likelihood of an event or outcome.","key":"CIS_WEP","name":"CIS-CTI Words of Estimative Probability","namespace":"basic","values":[{"definition":"Probability < 0.05. Almost no chance, remote","key":"ANC","name":"Almost No Chance"},{"definition":"0.05 <= Probability < 0.20. Very unlikely, highly improbable.","key":"VU","name":"Very Unlikely"},{"definition":"0.20 <= Probability < 0.45. Unlikely, improbable.","key":"U","name":"Unlikely"},{"definition":"0.45 <= Probability < 0.55. Roughly even chance, roughly even odds.","key":"REC","name":"Roughly Even Chance"},{"definition":"0.55 <= Probability < 0.80. Likely, probable.","key":"L","name":"Likely"},{"definition":"0.80 <= Probability < 0.95. Very likely, highly probable.","key":"VL","name":"Very Likely"},{"definition":"0.95 <= Probability. Almost certain, nearly certain.","key":"AC","name":"Almost Certain"}],"version":"1.0.0"},{"definition":"The Eisenhower outcome group.","key":"IKE","name":"Do, Schedule, Delegate, Delete","namespace":"basic","values":[{"definition":"Delete","key":"D","name":"Delete"},{"definition":"Delegate","key":"G","name":"Delegate"},{"definition":"Schedule","key":"S","name":"Schedule"},{"definition":"Do","key":"O","name":"Do"}],"version":"1.0.0"},{"definition":"A Low/Medium/High decision point / outcome group.","key":"LMH","name":"LowMediumHigh","namespace":"basic","values":[{"definition":"Low","key":"L","name":"Low"},{"definition":"Medium","key":"M","name":"Medium"},{"definition":"High","key":"H","name":"High"}],"version":"1.0.0"},{"definition":"A median split divides a distribution into two equal parts, with 50% of the values falling below the median and 50% above it.","key":"MEDIAN","name":"Median Split","namespace":"basic","values":[{"definition":"Quantile < 0.50. The lower half of the range of possible values.","key":"B","name":"Below Median"},{"definition":"0.50 <= Quantile <= 1.0. The upper half of the range of possible values.","key":"A","name":"Above Median"}],"version":"1.0.0"},{"definition":"The MoSCoW (Must, Should, Could, Won't) outcome group.","key":"MSCW","name":"MoSCoW","namespace":"basic","values":[{"definition":"Won't","key":"W","name":"Won't"},{"definition":"Could","key":"C","name":"Could"},{"definition":"Should","key":"S","name":"Should"},{"definition":"Must","key":"M","name":"Must"}],"version":"1.0.0"},{"definition":"A probability scale that divides between less than 50% and greater than or equal to 50%","key":"P_2A","name":"Probability Scale in 2 equal levels, ascending","namespace":"basic","values":[{"definition":"0.0 <= Probability < 0.5","key":"LT50","name":"Less than 50%"},{"definition":"0.5 <= Probability <= 1.0","key":"GT50","name":"Greater than 50%"}],"version":"1.0.0"},{"definition":"A probability scale with 20% increments","key":"P_5A","name":"Probability Scale in 5 equal levels, ascending","namespace":"basic","values":[{"definition":"Probability < 0.2","key":"P0_20","name":"Less than 20%"},{"definition":"0.2 <= Probability < 0.4","key":"P20_40","name":"20% to 40%"},{"definition":"0.4 <= Probability < 0.6","key":"P40_60","name":"40% to 60%"},{"definition":"0.6 <= Probability < 0.8","key":"P60_80","name":"60% to 80%"},{"definition":"0.8 <= Probability <= 1.0","key":"P80_100","name":"Greater than 80%"}],"version":"1.0.0"},{"definition":"A probability scale with higher resolution as probability increases","key":"P_5W","name":"Probability Scale in 5 weighted levels, ascending","namespace":"basic","values":[{"definition":"Probability < 0.3","key":"P0_30","name":"Less than 30%"},{"definition":"0.3 <= Probability < 0.55","key":"P30_55","name":"30% to 55%"},{"definition":"0.55 <= Probability < 0.75","key":"P55_75","name":"55% to 75%"},{"definition":"0.75 <= Probability < 0.9","key":"P75_90","name":"75% to 90%"},{"definition":"0.9 <= Probability <= 1.0","key":"P90_100","name":"Greater than 90%"}],"version":"1.0.0"},{"definition":"A quartile is one of four equal groups that a population can be divided into according to the distribution of values of a particular variable.","key":"QUARTILES","name":"Quartiles","namespace":"basic","values":[{"definition":"Quantile < 0.25. The lowest 25% of the range of possible values.","key":"Q1","name":"First Quartile"},{"definition":"0.25 <= Quantile < 0.50. The second lowest 25% of the range of possible values.","key":"Q2","name":"Second Quartile"},{"definition":"0.50 <= Quantile < 0.75. The second highest 25% of the range of possible values.","key":"Q3","name":"Third Quartile"},{"definition":"0.75 <= Quantile <= 1.0. The highest 25% of the range of possible values.","key":"Q4","name":"Fourth Quartile"}],"version":"1.0.0"},{"definition":"A quintile is one of five equal groups that a population can be divided into according to the distribution of values of a particular variable.","key":"QUINTILES","name":"Quintiles","namespace":"basic","values":[{"definition":"Quantile < 0.20. The lowest 20% of the range of possible values.","key":"Q1","name":"First Quintile"},{"definition":"0.20 <= Quantile < 0.40. The second lowest 20% of the range of possible values.","key":"Q2","name":"Second Quintile"},{"definition":"0.40 <= Quantile < 0.60. The middle 20% of the range of possible values.","key":"Q3","name":"Third Quintile"},{"definition":"0.60 <= Quantile < 0.80. The second highest 20% of the range of possible values.","key":"Q4","name":"Fourth Quintile"},{"definition":"0.80 <= Quantile <= 1.0. The highest 20% of the range of possible values.","key":"Q5","name":"Fifth Quintile"}],"version":"1.0.0"},{"definition":"The Value/Complexity outcome group.","key":"VALUE_COMPLEXITY","name":"Value, Complexity","namespace":"basic","values":[{"definition":"Drop","key":"D","name":"Drop"},{"definition":"Reconsider Later","key":"R","name":"Reconsider Later"},{"definition":"Easy Win","key":"E","name":"Easy Win"},{"definition":"Do First","key":"F","name":"Do First"}],"version":"1.0.0"},{"definition":"A Yes/No decision point / outcome group.","key":"YN","name":"YesNo","namespace":"basic","values":[{"definition":"No","key":"N","name":"No"},{"definition":"Yes","key":"Y","name":"Yes"}],"version":"1.0.0"},{"definition":"The CISA BOD 26-04 outcome group of remediation timelines for agencies to follow.","key":"BOD2604","name":"CISA BOD 26-04 Remediation Timelines","namespace":"cisa","values":[{"definition":"The vulnerability should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild.","key":"FSU","name":"Fix on system upgrade"},{"definition":"Remediate within 60 days.","key":"60D","name":"60 days"},{"definition":"Remediate within 14 days.","key":"14D","name":"14 days"},{"definition":"Remediate within 3 days.","key":"3D","name":"3 days"},{"definition":"Remediate within 3 days and carry out a forensic triage of the asset to assess whether the system is compromised.","key":"3DF","name":"3 days & forensic investigation"}],"version":"1.0.0"},{"definition":"The CISA outcome group. CISA uses its own SSVC decision tree model to prioritize relevant vulnerabilities into four possible decisions: Track, Track*, Attend, and Act.","key":"CISA","name":"CISA Levels","namespace":"cisa","values":[{"definition":"The vulnerability does not require action at this time. The organization would continue to track the vulnerability and reassess it if new information becomes available. CISA recommends remediating Track vulnerabilities within standard update timelines.","key":"T","name":"Track"},{"definition":"The vulnerability contains specific characteristics that may require closer monitoring for changes. CISA recommends remediating Track* vulnerabilities within standard update timelines.","key":"T*","name":"Track*"},{"definition":"The vulnerability requires attention from the organization's internal, supervisory-level individuals. Necessary actions may include requesting assistance or information about the vulnerability and may involve publishing a notification, either internally and/or externally, about the vulnerability. CISA recommends remediating Attend vulnerabilities sooner than standard update timelines.","key":"AT","name":"Attend"},{"definition":"The vulnerability requires attention from the organization's internal, supervisory-level and leadership-level individuals. Necessary actions include requesting assistance or information about the vulnerability, as well as publishing a notification either internally and/or externally. Typically, internal groups would meet to determine the overall response and then execute agreed upon actions. CISA recommends remediating Act vulnerabilities as soon as possible.","key":"AC","name":"Act"}],"version":"1.1.0"},{"definition":"Denotes whether a vulnerability is in the CISA Known Exploited Vulnerabilities (KEV) list.","key":"KEV","name":"In KEV","namespace":"cisa","values":[{"definition":"Vulnerability is not listed in KEV.","key":"N","name":"No"},{"definition":"Vulnerability is listed in KEV.","key":"Y","name":"Yes"}],"version":"1.0.0"},{"definition":"Prevalence of the mission essential functions","key":"MP","name":"Mission Prevalence","namespace":"cisa","values":[{"definition":"Neither Support nor Essential apply. The vulnerable component may be used within the entities, but it is not used as a mission-essential component, nor does it provide impactful support to mission-essential functions.","key":"M","name":"Minimal"},{"definition":"The vulnerable component only supports MEFs for two or more entities.","key":"S","name":"Support"},{"definition":"The vulnerable component directly provides capabilities that constitute at least one MEF for at least one entity; component failure may (but does not necessarily) lead to overall mission failure.","key":"E","name":"Essential"}],"version":"1.0.0"},{"definition":"Denotes whether the asset is accessible to unauthenticated or untrusted entities via public networks.","key":"PE","name":"Publicly Exposed","namespace":"cisa","values":[{"definition":"The asset is not accessible to unauthenticated or untrusted entities via public networks, such as the internet, regardless of its physical or logical location.","key":"N","name":"No"},{"definition":"The asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet, regardless of its physical or logical location.","key":"Y","name":"Yes"}],"version":"1.0.0"},{"definition":"This metric measures the impact to availability of a successfully exploited vulnerability.","key":"A","name":"Availability Impact","namespace":"cvss","values":[{"definition":"There is no impact to the availability of the system.","key":"N","name":"None"},{"definition":"There is reduced performance or interruptions in resource availability.","key":"L","name":"Low"},{"definition":"There is 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).","key":"H","name":"High"}],"version":"2.0.0"},{"definition":"This metric captures measurable actions that must be taken by the attacker to actively evade or circumvent existing built-in security-enhancing conditions in order to obtain a working exploit. ","key":"AC","name":"Attack Complexity","namespace":"cvss","values":[{"definition":"The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques. The attacker must have additional methods available to bypass security measures in place.","key":"H","name":"High"},{"definition":"The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system. ","key":"L","name":"Low"}],"version":"3.0.1"},{"definition":"This metric enables the consumer to customize the assessment depending on the importance of the affected IT asset to the analyst’s organization, measured in terms of Availability.","key":"AR","name":"Availability Requirement","namespace":"cvss","values":[{"definition":"Loss of availability is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).","key":"L","name":"Low"},{"definition":"Loss of availability is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).","key":"M","name":"Medium"},{"definition":"Loss of availability is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).","key":"H","name":"High"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"}],"version":"1.1.1"},{"definition":"This metric enables the consumer to customize the assessment depending on the importance of the affected IT asset to the analyst’s organization, measured in terms of Availability. This version does not include the Not Defined (X) option.","key":"AR_NoX","name":"Availability Requirement (without Not Defined)","namespace":"cvss","values":[{"definition":"Loss of availability is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).","key":"L","name":"Low"},{"definition":"Loss of availability is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).","key":"M","name":"Medium"},{"definition":"Loss of availability is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).","key":"H","name":"High"}],"version":"1.1.1"},{"definition":"This metric captures the prerequisite deployment and execution conditions or variables of the vulnerable system that enable the attack.","key":"AT","name":"Attack Requirements","namespace":"cvss","values":[{"definition":"The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack.","key":"P","name":"Present"},{"definition":"The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.","key":"N","name":"None"}],"version":"1.0.0"},{"definition":"The \"Automatable\" metric captures the answer to the question \"Can an attacker automate exploitation events for this vulnerability across multiple targets?\" based on steps 1-4 of the kill chain.","key":"AU","name":"Automatable","namespace":"cvss","values":[{"definition":"Attackers cannot reliably automate all 4 steps of the kill chain for this vulnerability for some reason. These steps are reconnaissance, weaponization, delivery, and exploitation.","key":"N","name":"No"},{"definition":"Attackers can reliably automate all 4 steps of the kill chain. These steps are reconnaissance, weaponization, delivery, and exploitation (e.g., the vulnerability is \"wormable\").","key":"Y","name":"Yes"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"}],"version":"1.0.0"},{"definition":"This metric reflects the context by which vulnerability exploitation is possible. This metric value (and consequently the resulting severity) will be larger the more remote (logically, and physically) an attacker can be in order to exploit the vulnerable system. The assumption is that the number of potential attackers for a vulnerability that could be exploited from across a network is larger than the number of potential attackers that could exploit a vulnerability requiring physical access to a device, and therefore warrants a greater severity.","key":"AV","name":"Attack Vector","namespace":"cvss","values":[{"definition":"The attack requires the attacker to physically touch or manipulate the vulnerable system. Physical interaction may be brief (e.g., evil maid attack1) or persistent.","key":"P","name":"Physical"},{"definition":"The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).","key":"L","name":"Local"},{"definition":"The vulnerable system is bound to a protocol 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 proximity (e.g., Bluetooth, NFC, or IEEE 802.11) or logical network (e.g., local IP subnet), or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN within an administrative network zone).","key":"A","name":"Adjacent"},{"definition":"The vulnerable system 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).","key":"N","name":"Network"}],"version":"3.0.1"},{"definition":"This metric measures the number of times an attacker must authenticate to a target in order to exploit a vulnerability. This metric does not gauge the strength or complexity of the authentication process, only that an attacker is required to provide credentials before an exploit may occur.  The possible values for this metric are listed in Table 3. The fewer authentication instances that are required, the higher the vulnerability score.","key":"Au","name":"Authentication","namespace":"cvss","values":[{"definition":"Exploiting the vulnerability requires that the attacker authenticate two or more times, even if the same credentials are used each time.","key":"M","name":"Multiple"},{"definition":"The vulnerability requires an attacker to be logged into the system (such as at a command line or via a desktop session or web interface).","key":"S","name":"Single"},{"definition":"Authentication is not required to exploit the vulnerability.","key":"N","name":"None"}],"version":"2.0.0"},{"definition":"This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.","key":"C","name":"Confidentiality Impact","namespace":"cvss","values":[{"definition":"There is no loss of confidentiality within the impacted component.","key":"N","name":"None"},{"definition":"There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is constrained. The information disclosure does not cause a direct, serious loss to the impacted component.","key":"L","name":"Low"},{"definition":"There is 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.","key":"H","name":"High"}],"version":"2.0.0"},{"definition":"This metric measures the potential for loss of life or physical assets.","key":"CDP","name":"Collateral Damage Potential","namespace":"cvss","values":[{"definition":"There is no potential for loss of life, physical assets, productivity or revenue.","key":"N","name":"None"},{"definition":"A successful exploit of this vulnerability may result in moderate physical or property damage or loss.","key":"LM","name":"Low-Medium"},{"definition":"A successful exploit of this vulnerability may result in significant physical or property damage or loss.","key":"MH","name":"Medium-High"},{"definition":"A successful exploit of this vulnerability may result in catastrophic physical or property damage and loss. The range of effect may be over a wide area.","key":"H","name":"High"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"ND","name":"Not Defined"}],"version":"2.0.0"},{"definition":"This metric enables the consumer to customize the assessment depending on the importance of the affected IT asset to the analyst’s organization, measured in terms of Confidentiality.","key":"CR","name":"Confidentiality Requirement","namespace":"cvss","values":[{"definition":"Loss of confidentiality is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).","key":"L","name":"Low"},{"definition":"Loss of confidentiality is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).","key":"M","name":"Medium"},{"definition":"Loss of confidentiality is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).","key":"H","name":"High"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"}],"version":"1.1.1"},{"definition":"This metric enables the consumer to customize the assessment depending on the importance of the affected IT asset to the analyst’s organization, measured in terms of Confidentiality. This version does not include the Not Defined (X) option.","key":"CR_NoX","name":"Confidentiality Requirement (without Not Defined)","namespace":"cvss","values":[{"definition":"Loss of confidentiality is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).","key":"L","name":"Low"},{"definition":"Loss of confidentiality is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).","key":"M","name":"Medium"},{"definition":"Loss of confidentiality is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).","key":"H","name":"High"}],"version":"1.1.1"},{"definition":"The CVSS Qualitative Severity Rating Scale group.","key":"CVSS","name":"CVSS Qualitative Severity Rating Scale","namespace":"cvss","values":[{"definition":"None (0.0)","key":"N","name":"None"},{"definition":"Low (0.1-3.9)","key":"L","name":"Low"},{"definition":"Medium (4.0-6.9)","key":"M","name":"Medium"},{"definition":"High (7.0-8.9)","key":"H","name":"High"},{"definition":"Critical (9.0-10.0)","key":"C","name":"Critical"}],"version":"1.0.0"},{"definition":"This metric measures the likelihood of the vulnerability being attacked, and is based on the current state of exploit techniques, exploit code availability, or active, “in-the-wild” exploitation.","key":"E","name":"Exploit Maturity","namespace":"cvss","values":[{"definition":"Based on available threat intelligence each of the following must apply: No knowledge of publicly available proof-of-concept exploit code No knowledge of reported attempts to exploit this vulnerability No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability (i.e., neither the “POC” nor “Attacked” values apply)","key":"U","name":"Unreported"},{"definition":"Based on available threat intelligence each of the following must apply: Proof-of-concept exploit code is publicly available No knowledge of reported attempts to exploit this vulnerability No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability (i.e., the “Attacked” value does not apply)","key":"P","name":"Proof-of-Concept"},{"definition":"Based on available threat intelligence either of the following must apply: Attacks targeting this vulnerability (attempted or successful) have been reported Solutions to simplify attempts to exploit the vulnerability are publicly or privately available (such as exploit toolkits)","key":"A","name":"Attacked"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"}],"version":"2.0.0"},{"definition":"AV/PR/UI with 3 levels specified in Table 24","key":"EQ1","name":"Equivalence Set 1","namespace":"cvss","values":[{"definition":"2: AV:P or not(AV:N or PR:N or UI:N)","key":"L","name":"Low"},{"definition":"1: (AV:N or PR:N or UI:N) and not (AV:N and PR:N and UI:N) and not AV:P","key":"M","name":"Medium"},{"definition":"0: AV:N and PR:N and UI:N","key":"H","name":"High"}],"version":"1.0.0"},{"definition":"AC/AT with 2 levels specified in Table 25","key":"EQ2","name":"Equivalence Set 2","namespace":"cvss","values":[{"definition":"1: not (AC:L and AT:N)","key":"L","name":"Low"},{"definition":"0: AC:L and AT:N","key":"H","name":"High"}],"version":"1.0.0"},{"definition":"VC/VI/VA with 3 levels specified in Table 26","key":"EQ3","name":"Equivalence Set 3","namespace":"cvss","values":[{"definition":"2: not (VC:H or VI:H or VA:H)","key":"L","name":"Low"},{"definition":"1: not (VC:H and VI:H) and (VC:H or VI:H or VA:H)","key":"M","name":"Medium"},{"definition":"0: VC:H and VI:H","key":"H","name":"High"}],"version":"1.0.0"},{"definition":"SC/SI/SA with 3 levels specified in Table 27","key":"EQ4","name":"Equivalence Set 4","namespace":"cvss","values":[{"definition":"2: not (MSI:S or MSA:S) and not (SC:H or SI:H or SA:H)","key":"L","name":"Low"},{"definition":"1: not (MSI:S or MSA:S) and (SC:H or SI:H or SA:H)","key":"M","name":"Medium"},{"definition":"0: MSI:S or MSA:S","key":"H","name":"High"}],"version":"1.0.0"},{"definition":"E with 3 levels specified in Table 28","key":"EQ5","name":"Equivalence Set 5","namespace":"cvss","values":[{"definition":"2: E:U","key":"L","name":"Low"},{"definition":"1: E:P","key":"M","name":"Medium"},{"definition":"0: E:A","key":"H","name":"High"}],"version":"1.0.0"},{"definition":"VC/VI/VA+CR/CI/CA with 2 levels specified in Table 29","key":"EQ6","name":"Equivalence Set 6","namespace":"cvss","values":[{"definition":"1: not (CR:H and VC:H) and not (IR:H and VI:H) and not (AR:H and VA:H)","key":"L","name":"Low"},{"definition":"0: (CR:H and VC:H) or (IR:H and VI:H) or (AR:H and VA:H)","key":"H","name":"High"}],"version":"1.0.0"},{"definition":"This metric measures the likelihood of the vulnerability being attacked, and is based on the current state of exploit techniques, exploit code availability, or active, “in-the-wild” exploitation. This version does not include the Not Defined (X) option.","key":"E_NoX","name":"Exploit Maturity (without Not Defined)","namespace":"cvss","values":[{"definition":"Based on available threat intelligence each of the following must apply: No knowledge of publicly available proof-of-concept exploit code No knowledge of reported attempts to exploit this vulnerability No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability (i.e., neither the “POC” nor “Attacked” values apply)","key":"U","name":"Unreported"},{"definition":"Based on available threat intelligence each of the following must apply: Proof-of-concept exploit code is publicly available No knowledge of reported attempts to exploit this vulnerability No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability (i.e., the “Attacked” value does not apply)","key":"P","name":"Proof-of-Concept"},{"definition":"Based on available threat intelligence either of the following must apply: Attacks targeting this vulnerability (attempted or successful) have been reported Solutions to simplify attempts to exploit the vulnerability are publicly or privately available (such as exploit toolkits)","key":"A","name":"Attacked"}],"version":"2.0.0"},{"definition":"This metric measures the impact to integrity of a successfully exploited vulnerability.","key":"I","name":"Integrity Impact","namespace":"cvss","values":[{"definition":"There is no impact to the integrity of the system.","key":"N","name":"None"},{"definition":"Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is constrained. The data modification does not have a direct, serious impact on the impacted component.","key":"L","name":"Low"},{"definition":"There is a total loss of integrity, or a complete loss of protection.","key":"H","name":"High"}],"version":"2.0.0"},{"definition":"This metric measures the impact bias of the vulnerability.","key":"IB","name":"Impact Bias","namespace":"cvss","values":[{"definition":"Confidentiality Impact, Integrity Impact, and Availability Impact are all assigned the same weight.","key":"N","name":"Normal"},{"definition":"Confidentiality impact is assigned greater weight than Integrity Impact or Availability Impact.","key":"C","name":"Confidentiality"},{"definition":"Integrity Impact is assigned greater weight than Confidentiality Impact or Availability Impact.","key":"I","name":"Integrity"},{"definition":"Availability Impact is assigned greater weight than Confidentiality Impact or Integrity Impact.","key":"A","name":"Availability"}],"version":"1.0.0"},{"definition":"This metric enables the consumer to customize the assessment depending on the importance of the affected IT asset to the analyst’s organization, measured in terms of Confidentiality.","key":"IR","name":"Integrity Requirement","namespace":"cvss","values":[{"definition":"Loss of integrity is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).","key":"L","name":"Low"},{"definition":"Loss of integrity is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).","key":"M","name":"Medium"},{"definition":"Loss of integrity is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).","key":"H","name":"High"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"}],"version":"1.1.1"},{"definition":"This metric enables the consumer to customize the assessment depending on the importance of the affected IT asset to the analyst’s organization, measured in terms of Confidentiality. This version does not include the Not Defined (X) option.","key":"IR_NoX","name":"Integrity Requirement (without Not Defined)","namespace":"cvss","values":[{"definition":"Loss of integrity is likely to have only a limited adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).","key":"L","name":"Low"},{"definition":"Loss of integrity is likely to have a serious adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).","key":"M","name":"Medium"},{"definition":"Loss of integrity is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).","key":"H","name":"High"}],"version":"1.1.1"},{"definition":"This metric measures the impact to availability of a successfully exploited vulnerability.","key":"MA","name":"Modified Availability Impact","namespace":"cvss","values":[{"definition":"There is no impact to the availability of the system.","key":"N","name":"None"},{"definition":"There is reduced performance or interruptions in resource availability.","key":"L","name":"Low"},{"definition":"There is 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).","key":"H","name":"High"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"}],"version":"2.0.0"},{"definition":"This metric captures measurable actions that must be taken by the attacker to actively evade or circumvent existing built-in security-enhancing conditions in order to obtain a working exploit. ","key":"MAC","name":"Modified Attack Complexity","namespace":"cvss","values":[{"definition":"The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques. The attacker must have additional methods available to bypass security measures in place.","key":"H","name":"High"},{"definition":"The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system. ","key":"L","name":"Low"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"}],"version":"3.0.1"},{"definition":"This metric captures the prerequisite deployment and execution conditions or variables of the vulnerable system that enable the attack.","key":"MAT","name":"Modified Attack Requirements","namespace":"cvss","values":[{"definition":"The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack.","key":"P","name":"Present"},{"definition":"The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.","key":"N","name":"None"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"}],"version":"1.0.0"},{"definition":"This metric reflects the context by which vulnerability exploitation is possible. This metric value (and consequently the resulting severity) will be larger the more remote (logically, and physically) an attacker can be in order to exploit the vulnerable system. The assumption is that the number of potential attackers for a vulnerability that could be exploited from across a network is larger than the number of potential attackers that could exploit a vulnerability requiring physical access to a device, and therefore warrants a greater severity.","key":"MAV","name":"Modified Attack Vector","namespace":"cvss","values":[{"definition":"The attack requires the attacker to physically touch or manipulate the vulnerable system. Physical interaction may be brief (e.g., evil maid attack1) or persistent.","key":"P","name":"Physical"},{"definition":"The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).","key":"L","name":"Local"},{"definition":"The vulnerable system is bound to a protocol 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 proximity (e.g., Bluetooth, NFC, or IEEE 802.11) or logical network (e.g., local IP subnet), or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN within an administrative network zone).","key":"A","name":"Adjacent"},{"definition":"The vulnerable system 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).","key":"N","name":"Network"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"}],"version":"3.0.1"},{"definition":"This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.","key":"MC","name":"Modified Confidentiality Impact","namespace":"cvss","values":[{"definition":"There is no loss of confidentiality within the impacted component.","key":"N","name":"None"},{"definition":"There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is constrained. The information disclosure does not cause a direct, serious loss to the impacted component.","key":"L","name":"Low"},{"definition":"There is 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.","key":"H","name":"High"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"}],"version":"2.0.0"},{"definition":"This metric measures the impact to integrity of a successfully exploited vulnerability.","key":"MI","name":"Modified Integrity Impact","namespace":"cvss","values":[{"definition":"There is no impact to the integrity of the system.","key":"N","name":"None"},{"definition":"Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is constrained. The data modification does not have a direct, serious impact on the impacted component.","key":"L","name":"Low"},{"definition":"There is a total loss of integrity, or a complete loss of protection.","key":"H","name":"High"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"}],"version":"2.0.0"},{"definition":"This metric describes the level of privileges an attacker must possess prior to successfully exploiting the vulnerability. The method by which the attacker obtains privileged credentials prior to the attack (e.g., free trial accounts), is outside the scope of this metric. Generally, self-service provisioned accounts do not constitute a privilege requirement if the attacker can grant themselves privileges as part of the attack.","key":"MPR","name":"Modified Privileges Required","namespace":"cvss","values":[{"definition":"The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.","key":"H","name":"High"},{"definition":"The attacker is authorized with (i.e., requires) privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.","key":"L","name":"Low"},{"definition":"The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.","key":"N","name":"None"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"}],"version":"1.0.1"},{"definition":"the ability for a vulnerability in one software component to impact resources beyond its means, or privileges","key":"MS","name":"Modified Scope","namespace":"cvss","values":[{"definition":"An exploited vulnerability can only affect resources managed by the same authority. In this case the vulnerable component and the impacted component are the same.","key":"U","name":"Unchanged"},{"definition":"An exploited vulnerability can affect resources beyond the authorization privileges intended by the vulnerable component. In this case the vulnerable component and the impacted component are different.","key":"C","name":"Changed"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"}],"version":"1.0.0"},{"definition":"This metric measures the impact on availability a successful exploit of the vulnerability will have on the Subsequent System.","key":"MSA","name":"Modified Availability Impact to the Subsequent System","namespace":"cvss","values":[{"definition":"There is negligible impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.","key":"N","name":"Negligible"},{"definition":"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.","key":"L","name":"Low"},{"definition":"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).","key":"H","name":"High"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"},{"definition":"The Safety metric value measures the impact regarding the Safety of a human actor or participant that can be predictably injured as a result of the vulnerability being exploited.","key":"S","name":"Safety"}],"version":"1.0.1"},{"definition":"This metric measures the impact on availability a successful exploit of the vulnerability will have on the Subsequent System. This version does not include the Not Defined (X) option.","key":"MSA_NoX","name":"Modified Availability Impact to the Subsequent System (without Not Defined)","namespace":"cvss","values":[{"definition":"There is negligible impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.","key":"N","name":"Negligible"},{"definition":"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.","key":"L","name":"Low"},{"definition":"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).","key":"H","name":"High"},{"definition":"The Safety metric value measures the impact regarding the Safety of a human actor or participant that can be predictably injured as a result of the vulnerability being exploited.","key":"S","name":"Safety"}],"version":"1.0.1"},{"definition":"This metric measures the impact to the confidentiality of the information managed by the system due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones. The resulting score is greatest when the loss to the system is highest.","key":"MSC","name":"Modified Confidentiality Impact to the Subsequent System","namespace":"cvss","values":[{"definition":"There is negligible loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.","key":"N","name":"Negligible"},{"definition":"There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Subsequent System.","key":"L","name":"Low"},{"definition":"There is a total loss of confidentiality, resulting in all resources within the Subsequent System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.","key":"H","name":"High"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"}],"version":"1.0.1"},{"definition":"This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. Integrity of a system is impacted when an attacker causes unauthorized modification of system data. Integrity is also impacted when a system user can repudiate critical actions taken in the context of the system (e.g. due to insufficient logging). The resulting score is greatest when the consequence to the system is highest.","key":"MSI","name":"Modified Integrity Impact to the Subsequent System","namespace":"cvss","values":[{"definition":"There is negligible loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.","key":"N","name":"Negligible"},{"definition":"Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Subsequent System.","key":"L","name":"Low"},{"definition":"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 Subsequent System. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the Subsequent System.","key":"H","name":"High"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"},{"definition":"The Safety metric value measures the impact regarding the Safety of a human actor or participant that can be predictably injured as a result of the vulnerability being exploited.","key":"S","name":"Safety"}],"version":"1.0.1"},{"definition":"This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. Integrity of a system is impacted when an attacker causes unauthorized modification of system data. Integrity is also impacted when a system user can repudiate critical actions taken in the context of the system (e.g. due to insufficient logging). The resulting score is greatest when the consequence to the system is highest. This version does not include the Not Defined (X) option.","key":"MSI_NoX","name":"Modified Integrity Impact to the Subsequent System (without Not Defined)","namespace":"cvss","values":[{"definition":"There is negligible loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.","key":"N","name":"Negligible"},{"definition":"Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Subsequent System.","key":"L","name":"Low"},{"definition":"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 Subsequent System. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the Subsequent System.","key":"H","name":"High"},{"definition":"The Safety metric value measures the impact regarding the Safety of a human actor or participant that can be predictably injured as a result of the vulnerability being exploited.","key":"S","name":"Safety"}],"version":"1.0.1"},{"definition":"This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable system. This metric determines whether the vulnerability can be exploited solely at the will of the attacker, or whether a separate user (or user-initiated process) must participate in some manner. The resulting score is greatest when no user interaction is required.","key":"MUI","name":"Modified User Interaction","namespace":"cvss","values":[{"definition":"Successful exploitation of this vulnerability requires a targeted user to perform specific, conscious interactions with the vulnerable system and the attacker’s payload, or the user’s interactions would actively subvert protection mechanisms which would lead to exploitation of the vulnerability.","key":"A","name":"Active"},{"definition":"Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.","key":"P","name":"Passive"},{"definition":"The vulnerable system can be exploited without interaction from any human user, other than the attacker.","key":"N","name":"None"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"}],"version":"2.0.0"},{"definition":"This metric measures the impact to the availability of the impacted system resulting from a successfully exploited vulnerability.","key":"MVA","name":"Modified Availability Impact to the Vulnerable System","namespace":"cvss","values":[{"definition":"There is no impact to availability within the Vulnerable System.","key":"N","name":"None"},{"definition":"There is reduced performance or 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 Vulnerable 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 Vulnerable System.","key":"L","name":"Low"},{"definition":"There is 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).","key":"H","name":"High"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"}],"version":"3.0.0"},{"definition":"This metric measures the impact to the confidentiality of the information managed by the system due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones.","key":"MVC","name":"Modified Confidentiality Impact to the Vulnerable System","namespace":"cvss","values":[{"definition":"There is no loss of confidentiality within the impacted component.","key":"N","name":"None"},{"definition":"There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is constrained. The information disclosure does not cause a direct, serious loss to the impacted component.","key":"L","name":"Low"},{"definition":"There is 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.","key":"H","name":"High"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"}],"version":"3.0.0"},{"definition":"This metric measures the impact to integrity of a successfully exploited vulnerability.","key":"MVI","name":"Modified Integrity Impact to the Vulnerable System","namespace":"cvss","values":[{"definition":"There is no loss of integrity within the Vulnerable System.","key":"N","name":"None"},{"definition":"Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.","key":"L","name":"Low"},{"definition":"There is a total loss of integrity, or a complete loss of protection.","key":"H","name":"High"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"}],"version":"3.0.0"},{"definition":"This metric describes the level of privileges an attacker must possess prior to successfully exploiting the vulnerability. The method by which the attacker obtains privileged credentials prior to the attack (e.g., free trial accounts), is outside the scope of this metric. Generally, self-service provisioned accounts do not constitute a privilege requirement if the attacker can grant themselves privileges as part of the attack.","key":"PR","name":"Privileges Required","namespace":"cvss","values":[{"definition":"The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.","key":"H","name":"High"},{"definition":"The attacker is authorized with (i.e., requires) privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.","key":"L","name":"Low"},{"definition":"The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.","key":"N","name":"None"}],"version":"1.0.1"},{"definition":"The CVSS Qualitative Severity Rating Scale provides a categorical representation of a CVSS Score.","key":"QS","name":"CVSS Qualitative Severity Rating Scale","namespace":"cvss","values":[{"definition":"No severity rating (0.0)","key":"N","name":"None"},{"definition":"Low (0.1 - 3.9)","key":"L","name":"Low"},{"definition":"Medium (4.0 - 6.9)","key":"M","name":"Medium"},{"definition":"High (7.0 - 8.9)","key":"H","name":"High"},{"definition":"Critical (9.0 - 10.0)","key":"C","name":"Critical"}],"version":"1.0.0"},{"definition":"The Recovery metric describes the resilience of a system to recover services, in terms of performance and availability, after an attack has been performed.","key":"R","name":"Recovery","namespace":"cvss","values":[{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"},{"definition":"The system recovers services automatically after an attack has been performed.","key":"A","name":"Automatic"},{"definition":"The system requires manual intervention by the user to recover services, after an attack has been performed.","key":"U","name":"User"},{"definition":"The system services are irrecoverable by the user, after an attack has been performed.","key":"I","name":"Irrecoverable"}],"version":"1.0.0"},{"definition":"This metric measures the degree of confidence in the existence of the vulnerability and the credibility of the known technical details.","key":"RC","name":"Report Confidence","namespace":"cvss","values":[{"definition":"There are reports of impacts that indicate a vulnerability is present. The reports indicate that the cause of the vulnerability is unknown, or reports may differ on the cause or impacts of the vulnerability. Reporters are uncertain of the true nature of the vulnerability, and there is little confidence in the validity of the reports or whether a static Base score can be applied given the differences described.","key":"U","name":"Unknown"},{"definition":"Significant details are published, but researchers either do not have full confidence in the root cause, or do not have access to source code to fully confirm all of the interactions that may lead to the result. Reasonable confidence exists, however, that the bug is reproducible and at least one impact is able to be verified (proof-of-concept exploits may provide this).","key":"R","name":"Reasonable"},{"definition":"Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.","key":"C","name":"Confirmed"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"}],"version":"2.0.0"},{"definition":"The intention of the Vulnerability Response Effort metric is to provide supplemental information on how difficult it is for consumers to provide an initial response to the impact of vulnerabilities for deployed products and services in their infrastructure. The consumer can then take this additional information on effort required into consideration when applying mitigations and/or scheduling remediation.","key":"RE","name":"Vulnerability Response Effort","namespace":"cvss","values":[{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"},{"definition":"The effort required to respond to a vulnerability is low/trivial.","key":"L","name":"Low"},{"definition":"The actions required to respond to a vulnerability require some effort on behalf of the consumer and could cause minimal service impact to implement.","key":"M","name":"Moderate"},{"definition":"The actions required to respond to a vulnerability are significant and/or difficult, and may possibly lead to an extended, scheduled service impact. This would need to be considered for scheduling purposes including honoring any embargo on deployment of the selected response. Alternatively, response to the vulnerability in the field is not possible remotely. The only resolution to the vulnerability involves physical replacement (e.g. units deployed would have to be recalled for a depot level repair or replacement).","key":"H","name":"High"}],"version":"1.0.0"},{"definition":"This metric measures the remediation status of a vulnerability.","key":"RL","name":"Remediation Level","namespace":"cvss","values":[{"definition":"A complete vendor solution is available. Either the vendor has issued the final, official patch which eliminates the vulnerability or an upgrade that is not vulnerable is available.","key":"OF","name":"Official Fix"},{"definition":"There is an official but temporary fix available. This includes instances where the vendor issues a temporary hotfix, tool or official workaround.","key":"TF","name":"Temporary Fix"},{"definition":"There is an unofficial, non-vendor solution available. In some cases, users of the affected technology will create a patch of their own or provide steps to work around or otherwise mitigate against the vulnerability. When it is generally accepted that these unofficial fixes are adequate in plugging the hole for the mean time and no official remediation is available, this value can be set.","key":"W","name":"Workaround"},{"definition":"There is either no solution available or it is impossible to apply.","key":"U","name":"Unavailable"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"}],"version":"1.1.0"},{"definition":"the ability for a vulnerability in one software component to impact resources beyond its means, or privileges","key":"S","name":"Scope","namespace":"cvss","values":[{"definition":"An exploited vulnerability can only affect resources managed by the same authority. In this case the vulnerable component and the impacted component are the same.","key":"U","name":"Unchanged"},{"definition":"An exploited vulnerability can affect resources beyond the authorization privileges intended by the vulnerable component. In this case the vulnerable component and the impacted component are different.","key":"C","name":"Changed"}],"version":"1.0.0"},{"definition":"This metric measures the impact on availability a successful exploit of the vulnerability will have on the Subsequent System.","key":"SA","name":"Availability Impact to the Subsequent System","namespace":"cvss","values":[{"definition":"There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.","key":"N","name":"None"},{"definition":"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.","key":"L","name":"Low"},{"definition":"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).","key":"H","name":"High"}],"version":"1.0.0"},{"definition":"This metric measures the impact to the confidentiality of the information managed by the system due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones. The resulting score is greatest when the loss to the system is highest.","key":"SC","name":"Confidentiality Impact to the Subsequent System","namespace":"cvss","values":[{"definition":"There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.","key":"N","name":"Negligible"},{"definition":"There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Subsequent System.","key":"L","name":"Low"},{"definition":"There is a total loss of confidentiality, resulting in all resources within the Subsequent System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.","key":"H","name":"High"}],"version":"1.0.0"},{"definition":"The Safety decision point is a measure of the potential for harm to humans or the environment.","key":"SF","name":"Safety","namespace":"cvss","values":[{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"},{"definition":"Consequences of the vulnerability meet definition of IEC 61508 consequence categories of \"marginal,\" \"critical,\" or \"catastrophic.\"","key":"P","name":"Present"},{"definition":"Consequences of the vulnerability meet definition of IEC 61508 consequence category \"negligible.\"","key":"N","name":"Negligible"}],"version":"1.0.0"},{"definition":"This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information. Integrity of a system is impacted when an attacker causes unauthorized modification of system data. Integrity is also impacted when a system user can repudiate critical actions taken in the context of the system (e.g. due to insufficient logging). The resulting score is greatest when the consequence to the system is highest.","key":"SI","name":"Integrity Impact to the Subsequent System","namespace":"cvss","values":[{"definition":"There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.","key":"N","name":"None"},{"definition":"Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Subsequent System.","key":"L","name":"Low"},{"definition":"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 Subsequent System. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the Subsequent System.","key":"H","name":"High"}],"version":"1.0.0"},{"definition":"This metric measures the relative size of the field of target systems susceptible to the vulnerability. It is meant as an environment-specific indicator in order to approximate the percentage of systems within the environment that could be affected by the vulnerability.","key":"TD","name":"Target Distribution","namespace":"cvss","values":[{"definition":"No target systems exist, or targets are so highly specialized that they only exist in a laboratory setting. Effectively 0% of the environment is at risk.","key":"N","name":"None"},{"definition":"Targets exist inside the environment, but on a small scale. Between 1% - 15% of the total environment is at risk.","key":"L","name":"Low"},{"definition":"Targets exist inside the environment, but on a medium scale. Between 16% - 49% of the total environment is at risk.","key":"M","name":"Medium"},{"definition":"Targets exist inside the environment on a considerable scale. Between 50% - 100% of the total environment is considered at risk.","key":"H","name":"High"},{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"}],"version":"1.1.0"},{"definition":"Many vendors currently provide supplemental severity ratings to consumers via product security advisories. Other vendors publish Qualitative Severity Ratings from the CVSS Specification Document in their advisories. To facilitate a standardized method to incorporate additional provider-supplied assessment, an optional \"pass-through\" Supplemental Metric called Provider Urgency is available.","key":"U","name":"Provider Urgency","namespace":"cvss","values":[{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"},{"definition":"Provider has assessed the impact of this vulnerability as having no urgency (Informational).","key":"C","name":"Clear"},{"definition":"Provider has assessed the impact of this vulnerability as having a reduced urgency.","key":"G","name":"Green"},{"definition":"Provider has assessed the impact of this vulnerability as having a moderate urgency.","key":"A","name":"Amber"},{"definition":"Provider has assessed the impact of this vulnerability as having the highest urgency.","key":"R","name":"Red"}],"version":"1.0.0"},{"definition":"This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable system. This metric determines whether the vulnerability can be exploited solely at the will of the attacker, or whether a separate user (or user-initiated process) must participate in some manner. The resulting score is greatest when no user interaction is required.","key":"UI","name":"User Interaction","namespace":"cvss","values":[{"definition":"Successful exploitation of this vulnerability requires a targeted user to perform specific, conscious interactions with the vulnerable system and the attacker’s payload, or the user’s interactions would actively subvert protection mechanisms which would lead to exploitation of the vulnerability.","key":"A","name":"Active"},{"definition":"Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.","key":"P","name":"Passive"},{"definition":"The vulnerable system can be exploited without interaction from any human user, other than the attacker.","key":"N","name":"None"}],"version":"2.0.0"},{"definition":"Value Density describes the resources that the attacker will gain control over with a single exploitation event. It has two possible values, diffuse and concentrated.","key":"V","name":"Value Density","namespace":"cvss","values":[{"definition":"This metric value is not defined. See CVSS documentation for details.","key":"X","name":"Not Defined"},{"definition":"The vulnerable system has limited resources. That is, the resources that the attacker will gain control over with a single exploitation event are relatively small.","key":"D","name":"Diffuse"},{"definition":"The vulnerable system is rich in resources. Heuristically, such systems are often the direct responsibility of \"system operators\" rather than users.","key":"C","name":"Concentrated"}],"version":"1.0.0"},{"definition":"This metric measures the impact to the availability of the impacted system resulting from a successfully exploited vulnerability.","key":"VA","name":"Availability Impact to the Vulnerable System","namespace":"cvss","values":[{"definition":"There is no impact to availability within the Vulnerable System.","key":"N","name":"None"},{"definition":"There is reduced performance or 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 Vulnerable 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 Vulnerable System.","key":"L","name":"Low"},{"definition":"There is 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).","key":"H","name":"High"}],"version":"3.0.0"},{"definition":"This metric measures the impact to the confidentiality of the information managed by the system due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones.","key":"VC","name":"Confidentiality Impact to the Vulnerable System","namespace":"cvss","values":[{"definition":"There is no loss of confidentiality within the impacted component.","key":"N","name":"None"},{"definition":"There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is constrained. The information disclosure does not cause a direct, serious loss to the impacted component.","key":"L","name":"Low"},{"definition":"There is 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.","key":"H","name":"High"}],"version":"3.0.0"},{"definition":"This metric measures the impact to integrity of a successfully exploited vulnerability.","key":"VI","name":"Integrity Impact to the Vulnerable System","namespace":"cvss","values":[{"definition":"There is no loss of integrity within the Vulnerable System.","key":"N","name":"None"},{"definition":"Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.","key":"L","name":"Low"},{"definition":"There is a total loss of integrity, or a complete loss of protection.","key":"H","name":"High"}],"version":"3.0.0"},{"definition":"A probability scale with finer resolution at both extremes, based on NIST SP 800-30 Rev. 1 Appendix G","key":"P_5X","name":"Probability Scale in 5 weighted levels, ascending","namespace":"nist#800-30","values":[{"definition":"0% <= Probability < 5%. Highly unlikely.","key":"VL","name":"Very Low"},{"definition":"5% <= Probability < 21%. Unlikely.","key":"L","name":"Low"},{"definition":"21% <= Probability < 80%. Somewhat likely.","key":"M","name":"Moderate"},{"definition":"80% <= Probability < 96%. Highly likely.","key":"H","name":"High"},{"definition":"96% <= Probability <= 100%. Almost certain.","key":"VH","name":"Very High"}],"version":"1.0.0"},{"definition":"Can an attacker reliably automate creating exploitation events for this vulnerability?","key":"A","name":"Automatable","namespace":"ssvc","values":[{"definition":"Attackers cannot reliably automate steps 1-4 of the kill chain for this vulnerability. These steps are (1) reconnaissance, (2) weaponization, (3) delivery, and (4) exploitation.","key":"N","name":"No"},{"definition":"Attackers can reliably automate steps 1-4 of the kill chain.","key":"Y","name":"Yes"}],"version":"2.0.0"},{"definition":"The coordinate outcome group.","key":"COORDINATE","name":"Decline, Track, Coordinate","namespace":"ssvc","values":[{"definition":"Do not act on the report.","key":"D","name":"Decline"},{"definition":"Receive information about the vulnerability and monitor for status changes but do not take any overt actions.","key":"T","name":"Track"},{"definition":"Take action on the report.","key":"C","name":"Coordinate"}],"version":"1.0.1"},{"definition":"Denotes whether a system meets a critical software definition.","key":"CS","name":"Critical Software","namespace":"ssvc","values":[{"definition":"System does not meet a critical software definition.","key":"N","name":"No"},{"definition":"System meets a critical software definition.","key":"Y","name":"Yes"}],"version":"1.0.0"},{"definition":"The original SSVC outcome group.","key":"DSOI","name":"Defer, Scheduled, Out-of-Cycle, Immediate","namespace":"ssvc","values":[{"definition":"Defer","key":"D","name":"Defer"},{"definition":"Scheduled","key":"S","name":"Scheduled"},{"definition":"Out-of-Cycle","key":"O","name":"Out-of-Cycle"},{"definition":"Immediate","key":"I","name":"Immediate"}],"version":"1.0.0"},{"definition":"The present state of exploitation of the vulnerability.","key":"E","name":"Exploitation","namespace":"ssvc","values":[{"definition":"There is no evidence of active exploitation and no public proof of concept (PoC) of how to exploit the vulnerability.","key":"N","name":"None"},{"definition":"One of the following is true: (1) Typical public PoC exists in sources such as Metasploit or websites like ExploitDB; or (2) the vulnerability has a well-known method of exploitation.","key":"P","name":"Public PoC"},{"definition":"Shared, observable, reliable evidence that the exploit is being used in the wild by real attackers; there is credible public reporting.","key":"A","name":"Active"}],"version":"1.1.0"},{"definition":"The Accessible Attack Surface of the Affected System or Service","key":"EXP","name":"System Exposure","namespace":"ssvc","values":[{"definition":"Local service or program; highly controlled network","key":"S","name":"Small"},{"definition":"Networked service with some access restrictions or mitigations already in place (whether locally or on the network). A successful mitigation must reliably interrupt the adversary’s attack, which requires the attack is detectable both reliably and quickly enough to respond. Controlled covers the situation in which a vulnerability can be exploited through chaining it with other vulnerabilities. The assumption is that the number of steps in the attack path is relatively low; if the path is long enough that it is implausible for an adversary to reliably execute it, then exposure should be small.","key":"C","name":"Controlled"},{"definition":"Internet or another widely accessible network where access cannot plausibly be restricted or controlled (e.g., DNS servers, web servers, VOIP servers, email servers)","key":"O","name":"Open"}],"version":"1.0.1"},{"definition":"Human Impact is a combination of Safety and Mission impacts.","key":"HI","name":"Human Impact","namespace":"ssvc","values":[{"definition":"Safety Impact:(Negligible) AND Mission Impact:(Degraded OR Crippled)","key":"L","name":"Low"},{"definition":"(Safety Impact:Negligible AND Mission Impact:MEF Failure) OR (Safety Impact:Marginal AND Mission Impact:(Degraded OR Crippled))","key":"M","name":"Medium"},{"definition":"(Safety Impact:Critical AND Mission Impact:(Degraded OR Crippled)) OR (Safety Impact:Marginal AND Mission Impact:MEF Failure)","key":"H","name":"High"},{"definition":"Safety Impact:Catastrophic OR Mission Impact:Mission Failure","key":"VH","name":"Very High"}],"version":"2.0.2"},{"definition":"Denotes whether a system meets a high value asset definition.","key":"HVA","name":"High Value Asset","namespace":"ssvc","values":[{"definition":"System does not meet a high value asset definition.","key":"N","name":"No"},{"definition":"System meets a high value asset definition.","key":"Y","name":"Yes"}],"version":"1.0.0"},{"definition":"Impact on Mission Essential Functions of the Organization","key":"MI","name":"Mission Impact","namespace":"ssvc","values":[{"definition":"Little to no impact up to degradation of non-essential functions; chronic degradation would eventually harm essential functions","key":"D","name":"Degraded"},{"definition":"Activities that directly support essential functions are crippled; essential functions continue for a time","key":"MSC","name":"MEF Support Crippled"},{"definition":"Any one mission essential function fails for period of time longer than acceptable; overall mission of the organization degraded but can still be accomplished for a time","key":"MEF","name":"MEF Failure"},{"definition":"Multiple or all mission essential functions fail; ability to recover those functions degraded; organization’s ability to deliver its overall mission fails","key":"MF","name":"Mission Failure"}],"version":"2.0.0"},{"definition":"Mission and Well-Being Impact is a combination of Mission Prevalence and Public Well-Being Impact.","key":"MWI","name":"Mission and Well-Being Impact","namespace":"ssvc","values":[{"definition":"Mission Prevalence:Minimal AND Public Well-Being Impact:Minimal","key":"L","name":"Low"},{"definition":"Mission Prevalence:Support AND Public Well-Being Impact:(Minimal OR Material)","key":"M","name":"Medium"},{"definition":"Mission Prevalence:Essential OR Public Well-Being Impact:(Irreversible)","key":"H","name":"High"}],"version":"1.0.0"},{"definition":"A coarse-grained representation of impact to public safety.","key":"PSI","name":"Public Safety Impact","namespace":"ssvc","values":[{"definition":"Safety Impact:Negligible","key":"M","name":"Minimal"},{"definition":"Safety Impact:(Marginal OR Critical OR Catastrophic)","key":"S","name":"Significant"}],"version":"2.0.1"},{"definition":"The publish outcome group.","key":"PUBLISH","name":"Publish, Do Not Publish","namespace":"ssvc","values":[{"definition":"Do Not Publish","key":"N","name":"Do Not Publish"},{"definition":"Publish","key":"P","name":"Publish"}],"version":"1.0.0"},{"definition":"How much value would a publication from the coordinator benefit the broader community?","key":"PVA","name":"Public Value Added","namespace":"ssvc","values":[{"definition":"Minimal value added to the existing public information because existing information is already high quality and in multiple outlets.","key":"L","name":"Limited"},{"definition":"Amplifies and/or augments the existing public information about the vulnerability, for example, adds additional detail, addresses or corrects errors in other public information, draws further attention to the vulnerability, etc.","key":"A","name":"Ampliative"},{"definition":"The publication would be the first publicly available, or be coincident with the first publicly available.","key":"P","name":"Precedence"}],"version":"1.0.0"},{"definition":"A coarse-grained representation of impact to public well-being.","key":"PWI","name":"Public Well-Being Impact","namespace":"ssvc","values":[{"definition":"The effect is below the threshold for all aspects described in material. ","key":"M","name":"Minimal"},{"definition":"Any one or more of these conditions hold. Physical harm: Does one or more of the following: (a) Causes physical distress or injury to system users. (b) Introduces occupational safety hazards. (c) Reduces and/or results in failure of cyber-physical system safety margins. Environment: Major externalities (property damage, environmental damage, etc.) are imposed on other parties. Financial: Financial losses likely lead to bankruptcy of multiple persons. Psychological: Widespread emotional or psychological harm, sufficient to necessitate counseling or therapy, impact populations of people. ","key":"MA","name":"Material"},{"definition":"Any one or more of these conditions hold. Physical harm: One or both of the following are true: (a) Multiple fatalities are likely.(b) The cyber-physical system, of which the vulnerable componen is a part, is likely lost or destroyed.  Environment: Extreme or serious externalities (immediate public health threat, environmental damage leading to small  ecosystem collapse, etc.) are imposed on other parties.  Financial: Social systems (elections, financial grid, etc.) supported by the software are destabilized and potentially collapse.  Psychological: N/A ","key":"I","name":"Irreversible"}],"version":"1.1.0"},{"definition":"Is the report credible?","key":"RC","name":"Report Credibility","namespace":"ssvc","values":[{"definition":"The report is not credible.","key":"NC","name":"Not Credible"},{"definition":"The report is credible.","key":"C","name":"Credible"}],"version":"1.0.0"},{"definition":"Is a viable report of the details of the vulnerability already publicly available?","key":"RP","name":"Report Public","namespace":"ssvc","values":[{"definition":"A public report of the vulnerability exists.","key":"Y","name":"Yes"},{"definition":"No public report of the vulnerability exists.","key":"N","name":"No"}],"version":"1.0.0"},{"definition":"How many suppliers are responsible for the vulnerable component and its remediation or mitigation plan?","key":"SC","name":"Supplier Cardinality","namespace":"ssvc","values":[{"definition":"There is only one supplier of the vulnerable component.","key":"O","name":"One"},{"definition":"There are multiple suppliers of the vulnerable component.","key":"M","name":"Multiple"}],"version":"1.0.0"},{"definition":"Has the reporter made a good-faith effort to contact the supplier of the vulnerable component using a quality contact method?","key":"SCON","name":"Supplier Contacted","namespace":"ssvc","values":[{"definition":"The supplier has not been contacted.","key":"N","name":"No"},{"definition":"The supplier has been contacted.","key":"Y","name":"Yes"}],"version":"1.0.0"},{"definition":"Is the supplier responding to the reporter’s contact effort and actively participating in the coordination effort?","key":"SE","name":"Supplier Engagement","namespace":"ssvc","values":[{"definition":"The supplier is responding to the reporter’s contact effort and actively participating in the coordination effort.","key":"A","name":"Active"},{"definition":"The supplier is not responding to the reporter’s contact effort and not actively participating in the coordination effort.","key":"U","name":"Unresponsive"}],"version":"1.0.0"},{"definition":"The safety impact of the vulnerability. (based on IEC 61508 with modifications)","key":"SI","name":"Safety Impact","namespace":"ssvc","values":[{"definition":"Any one or more of these conditions hold. **Physical harm**: Minor injuries at worst (IEC 61508 Negligible). **Operator resiliency**: Requires action by system operator to maintain safe system state as a result of exploitation of the vulnerability where operator actions would be well within expected operator abilities; OR causes a minor occupational safety hazard. **System resiliency**: Small reduction in built-in system safety margins; OR small reduction in system functional capabilities that support safe operation. **Environment**: Minor externalities (property damage, environmental damage, etc.) imposed on other parties. **Financial**: Financial losses, which are not readily absorbable, to multiple persons. **Psychological**: Emotional or psychological harm, sufficient to be cause for counselling or therapy, to multiple persons.","key":"N","name":"Negligible"},{"definition":"Any one or more of these conditions hold. **Physical harm**: Major injuries to one or more persons (IEC 61508 Marginal). **Operator resiliency**: Requires action by system operator to maintain safe system state as a result of exploitation of the vulnerability where operator actions would be within their capabilities but the actions require their full attention and effort; OR significant distraction or discomfort to operators; OR causes significant occupational safety hazard. **System resiliency**: System safety margin effectively eliminated but no actual harm; OR failure of system functional capabilities that support safe operation. **Environment**: Major externalities (property damage, environmental damage, etc.) imposed on other parties. **Financial**: Financial losses that likely lead to bankruptcy of multiple persons. **Psychological**: Widespread emotional or psychological harm, sufficient to be cause for counselling or therapy, to populations of people.","key":"M","name":"Marginal"},{"definition":"Any one or more of these conditions hold. **Physical harm**: Loss of life (IEC 61508 Critical). **Operator resiliency**: Actions that would keep the system in a safe state are beyond system operator capabilities, resulting in adverse conditions; OR great physical distress to system operators such that they cannot be expected to operate the system properly. **System resiliency**: Parts of the cyber-physical system break; system’s ability to recover lost functionality remains intact. **Environment**: Serious externalities (threat to life as well as property, widespread environmental damage, measurable public health risks, etc.) imposed on other parties. **Financial**: Socio-technical system (elections, financial grid, etc.) of which the affected component is a part is actively destabilized and enters unsafe state. **Psychological**: N/A.","key":"R","name":"Critical"},{"definition":"Any one or more of these conditions hold. **Physical harm**: Multiple loss of life (IEC 61508 Catastrophic). **Operator resiliency**: Operator incapacitated (includes fatality or otherwise incapacitated). **System resiliency**: Total loss of whole cyber-physical system, of which the software is a part. **Environment**: Extreme externalities (immediate public health threat, environmental damage leading to small ecosystem collapse, etc.) imposed on other parties. **Financial**: Social systems (elections, financial grid, etc.) supported by the software collapse. **Psychological**: N/A.","key":"C","name":"Catastrophic"}],"version":"2.0.1"},{"definition":"What is the state of the supplier’s work on addressing the vulnerability?","key":"SINV","name":"Supplier Involvement","namespace":"ssvc","values":[{"definition":"The supplier has provided a patch or fix.","key":"FR","name":"Fix Ready"},{"definition":"The supplier is actively generating a patch or fix; they may or may not have provided a mitigation or work-around in the mean time.","key":"C","name":"Cooperative"},{"definition":"The supplier has not responded, declined to generate a remediation, or no longer exists.","key":"UU","name":"Uncooperative/Unresponsive"}],"version":"1.0.0"},{"definition":"The technical impact of the vulnerability.","key":"TI","name":"Technical Impact","namespace":"ssvc","values":[{"definition":"The exploit gives the adversary limited control over, or information exposure about, the behavior of the software that contains the vulnerability. Or the exploit gives the adversary an importantly low stochastic opportunity for total control.","key":"P","name":"Partial"},{"definition":"The exploit gives the adversary total control over the behavior of the software, or it gives total disclosure of all information on the system that contains the vulnerability.","key":"T","name":"Total"}],"version":"1.0.0"},{"definition":"The Usefulness of the Exploit to the Adversary","key":"U","name":"Utility","namespace":"ssvc","values":[{"definition":"Automatable:No AND Value Density:Diffuse","key":"L","name":"Laborious"},{"definition":"(Automatable:Yes AND Value Density:Diffuse) OR (Automatable:No AND Value Density:Concentrated)","key":"E","name":"Efficient"},{"definition":"Automatable:Yes AND Value Density:Concentrated","key":"S","name":"Super Effective"}],"version":"1.0.1"},{"definition":"The speed at which the vulnerability can be exploited.","key":"V","name":"Virulence","namespace":"ssvc","values":[{"definition":"Steps 1-4 of the kill chain cannot be reliably automated for this vulnerability for some reason. These steps are reconnaissance, weaponization, delivery, and exploitation.","key":"S","name":"Slow"},{"definition":"Steps 1-4 of the of the kill chain can be reliably automated. If the vulnerability allows remote code execution or command injection, the default response should be rapid.","key":"R","name":"Rapid"}],"version":"1.0.0"},{"definition":"The concentration of value in the target","key":"VD","name":"Value Density","namespace":"ssvc","values":[{"definition":"The system that contains the vulnerable component has limited resources. That is, the resources that the adversary will gain control over with a single exploitation event are relatively small.","key":"D","name":"Diffuse"},{"definition":"The system that contains the vulnerable component is rich in resources. Heuristically, such systems are often the direct responsibility of “system operators” rather than users.","key":"C","name":"Concentrated"}],"version":"1.0.0"},{"definition":"PrioritizedRiskRemediation outcome group based on TheParanoids.","key":"PARANOIDS","name":"theParanoids","namespace":"x_com.yahooinc#prioritized-risk-remediation","values":[{"definition":"Track","key":"5","name":"Track 5"},{"definition":"Track Closely","key":"4","name":"Track Closely 4"},{"definition":"Attend","key":"3","name":"Attend 3"},{"definition":"Attend","key":"2","name":"Attend 2"},{"definition":"Act","key":"1","name":"Act 1"},{"definition":"Act ASAP","key":"0","name":"Act ASAP 0"}],"version":"1.0.0"}]}