Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit b51aeea

Browse files
committed
updates
1 parent 00c5ea2 commit b51aeea

File tree

3 files changed

+9
-7
lines changed

3 files changed

+9
-7
lines changed

docs/programs/images/severity-1a.png

12.5 KB
Loading

docs/programs/images/severity-2a.png

147 KB
Loading

docs/programs/severity.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,11 +6,15 @@ id: "programs/severity"
66

77
Reports are marked with a severity rating to show how severe the vulnerability is in the report submission form. The severity rating can be seen on reports, hacktivity, and in the inbox. On HackerOne, severity is particularly useful for structuring bounty ranges and is used when offering bounty recommendations. The severity level can be marked as:
88

9-
![severity-1](./images/severity-1.png)
9+
![severity-1](./images/severity-1a.png)
1010

11-
HackerOne utilizes the Common Vulnerability Scoring System (CVSS) - an industry standard calculator used to determine the severity of a bug. CVSS enables a common language around the severity of bugs. Hackers can either choose a severity level based on their own judgment of the vulnerability, or they can use the CVSS calculator to give more information about the vulnerability and calculate an exact CVSS score.
11+
HackerOne utilizes the Common Vulnerability Scoring System (CVSS) - an industry standard calculator used to determine the severity of a vulnerability. The CVSS enables a common language around the severity of vulnerabilities.
1212

13-
The CVSS Calculator provides a way to capture the principal characteristics of a vulnerability and produces a numerical score reflecting its severity. The numerical score is directly mapped to one of these descriptors: None, Low, Medium, High, Critical. These descriptors can then help you assess and prioritize your inbound vulnerabilities.
13+
>**Note:** It's optional for hackers to submit a severity rating.
14+
15+
Hackers can either choose a severity level based on their own judgment of the vulnerability, or they can use the CVSS calculator to give more information about the vulnerability and calculate an exact CVSS score.
16+
17+
The CVSS Calculator provides a way to capture the principal characteristics of a vulnerability and produces a numerical score reflecting its severity. The numerical score is directly mapped to one of these descriptors: *None, Low, Medium, High, Critical*. These descriptors can then help you assess and prioritize your inbound vulnerabilities.
1418

1519
There are 8 metrics defined for CVSS v3. The first 5 are about the attack method itself, while the latter three are dependent on how your program assesses impact - the direct consequence of a successful exploit. These are the different components to the CVSS Calculator:
1620

@@ -25,12 +29,10 @@ Confidentiality | The impact of the bug as it relates to confidential informatio
2529
Integrity | Whether the data can be modified due to the vulnerability.
2630
Availability | Whether data or functionality can be rendered inaccessible. The impact to the availability of the impacted component.
2731

28-
![severity-2](./images/severity-2.png)
32+
![severity-2](./images/severity-2a.png)
2933

30-
Instead of using the CVSS calculator, hackers can simply choose an estimated severity for the report.
34+
Instead of using the CVSS calculator, hackers can simply choose an estimated severity for the report by selecting whether the severity of a vulnerability is either *None, Low, Medium, High,* or *Critical*.
3135

3236
If your program has a custom methodology for determining severity, it's best to describe it on your Security Page.
3337

34-
><i>Note: It's optional for the hacker to submit a severity rating.</i>
35-
3638
You can read more details about CVSS [here](https://www.first.org/cvss/user-guide) or check out our [blog post](https://www.hackerone.com/blog/introducing-severity-cvss).

0 commit comments

Comments
 (0)