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

Skip to content

Commit 997191e

Browse files
committed
updates
1 parent be0e572 commit 997191e

File tree

2 files changed

+3
-3
lines changed

2 files changed

+3
-3
lines changed

docs/hackers/retesting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ To participate in the retest:
2727
* Are you able to reproduce the vulnerability?
2828
* Are you able to identify a bypass to the fix?
2929

30-
![retesting-3](./images/retesting-3c.png)
30+
![retesting questionnaire](./images/retesting-3c.png)
3131

3232
6. Submit a new report if you found a new vulnerability by clicking on the <b>submit a new report</b> link, and enter the report ID number in the <b>Report ID</b> field.
3333

docs/programs/retesting.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -42,15 +42,15 @@ The hacker will be asked to answer the following questions:
4242
* Are you able to reproduce the vulnerability?
4343
* Are you able to identify a bypass to the fix?
4444

45-
![retest questionnaire](./images/retesting-5b.png)
45+
![retest questionnaire](./images/retesting-5c.png)
4646

4747
If they were able to identify a bypass, they can can submit a new vulnerability report and enter the report ID in the questionnaire.
4848

4949
![submitting a new report through retest](./images/retesting-6b.png)
5050

5151
Hackers are also asked to provide a short summary of how they retested the vulnerability, and are also able to upload any attachments of their validations.
5252

53-
![summary and screenshots](./images/retesting-6c.png)
53+
![summary and screenshots](./images/retesting-6d.png)
5454

5555
Upon submission of the questionnaire, you’ll be notified that a hacker has completed a retest of your report within the report timeline and also through email.
5656

0 commit comments

Comments
 (0)