Request a reattack

1. Go to the intended group's Vulnerabilities section and choose the type of vulnerability in question.

   

2. In the Locations section, click on Select locations to reattack.
   




3. Select the vulnerability to be verified by the reattack. Only entries with the Vulnerable status and whose reattack status is neither Requested nor On hold are eligible. Then click on the Reattack button.
   

   


You may select multiple vulnerabilities and then click Reattack.

4. In the pop-up window, provide a detailed description (minimum 10 characters) of the fix you implemented to address the vulnerability.




If the reattack is to be performed by Fluid Attacks' tool, your justification does not need to be detailed. Read more about reattacks by the tool below.

5. Click Confirm. The Reattack column for that vulnerability then displays the value Requested.
   

   
   

To request reattacks from the To do section, follow these steps:

1. Go to the To do section.
   



2. Select the vulnerability by its check box and click on Reattack.
   



3. Provide a justification (minimum 10 characters) in the pop-up window and click Confirm.

On the platform, there are two possible reattack outcomes which are informed in the Reattack column of the Locations table.

1. Verified (vulnerable): The vulnerability is still exploitable. Fluid Attacks' tool or hacking team provide evidence of the exploit, accessible in the Evidence section. You should attempt remediation again and then request another reattack.
   
2. Verified (safe): The vulnerability has been successfully remediated.

Reattack outcomes are recorded in the type of vulnerability's Tracking and Consulting sections. 

Reattacks on hold

Reattacks might be temporarily delayed due to situations from your side, which Fluid Attacks calls "events." To learn more about them, read Resolve events impeding tests. Delayed reattacks are shown in the Locations table with the value On hold.

Reattacks for vulnerabilities detected by the automated tool

1. No detailed justification is needed in your request as the tool does not take it into account.
   
2. If you suspect a false positive or determine the finding poses no risk due to other security measures, contact Fluid Attacks or request the zero risk treatment, respectively, instead of a reattack.
   
3. The comments in Consulting sections are simple messages mentioning vulnerabilities present and remediated resulting from the reattack.
   
4. If you have trouble remedying the vulnerability, consult the vulnerability and fixes documentation for code examples or use the Fluid Attacks features that leverage generative artificial intelligence to have an idea of how to proceed.

Error when requesting reattacks

The platform prevents a reattack request if

1. the latest cloned version (last commit) of the repository associated with the vulnerability you are attempting to reattack is more than 1 day old, or
   
2. the vulnerability is still present in that last commit (or even in a previous commit).
   

These are the recommended steps when encountering this error:

1. Check the current version of the repository (in your remote version control system or remote container where the repository is hosted) and ensure the latest commit is recent and includes the fix.

2. Update the branch under evaluation (i.e., the one registered in the Scope section) to include the current version of the repository.

3. Return to the platform and request the reattack again.

4. If necessary, manually update the repository in Scope and request the reattack once its Status is OK.