Score
Jump to scoreCalculator
Bug Bounty Severity Calculator
This metric reflects the context by which vulnerability exploitation is possible. The Base Score increases the more remote (logically, and physically) an attacker can be in order to exploit the vulnerable component.
Select what type of vector
This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability. Such conditions may require the collection of more information about the target, the presence of certain system configuration settings, or computational exceptions.
Measurable effort to exploit
This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability. This Base Score increases as fewer privileges are required.
Requires privileged account
Does the attacker need extensive permissions?
This metric captures the requirement for a user, other than the attacker, to participate in the successful compromise of the vulnerable component. 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 Base Score is highest when no user interaction is required.
Victim performs an action during exploit?
Does a successful attack affect a system beyond those already in scope of the vulnerable system? If so, the Base Score increases and the Confidentiality, Integrity and Availability metrics should be scored relative to the impacted component.
Can the attacker impact a separate service?
This metric measures the impact to the confidentiality of the information resources managed by a software component 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.
Data impact?
Does this impact scale to the rest of the service?
This metric measures the impact to the integrity of a system or data due to a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information resources.
Data impact?
Does this impact scale to the rest of the service?
This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability. It refers to the loss of availability of the impacted component itself, such as a networked service (e.g., web, database, email). Since availability refers to the accessibility of information resources, attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of an impacted component.
Level of disruption to network service?
How much of the service is impacted?
Refer to the Scope page for details on which assets are considered Core and which assets are considered Non-Core.
Score
Score
0.0
Bounty
$ 0
*Not scalable to most or all of Shopify
Severity
None
Vector String