Test Vulnerability Remediation

Testing whether a fix works is an integral part of application security. You can try code changes and test whether they fix the vulnerability by replaying the attack from the Vulnerability Details window. To validate whether a remediation worked, you can also re-run the same scan that the vulnerability was found in.

Replay attack

You can replay the attack using the Rapid7 AppSec Plugin for Chrome browsers. Replaying attacks allows you to watch the attack traffic to determine whether a vulnerability is valid. You can also edit the request in the Request Builder to see if a change fixes or further validates a vulnerability.

In Application Security, you can access vulnerabilities and replay attacks from the scan report or vulnerability.

After installing the plugin, you can generate a scan report or view vulnerabilities within a scan and replay the attack.

Validate by scan report

  1. On the Apps page, select the app you want to validate.
  2. On the app details page, select the scan you want to generate a report for.
  3. Click Generate Report.
  4. Give the report a name and choose HTML export.
  5. When the report is available, replay the attack.
    1. Select an attack type and then click Replay Attack.
    2. In the Vulnerability Validator window, use the tabs at the top to switch between the steps in the attack traffic that occurred.
    3. On each tab, click Send to validate each attack with the Request Builder. The response headers and response body will return with the attack information.

Validate by vulnerability

  1. On the Apps page, select the app you want to validate.
  2. On the Vulnerabilities tab, select the vulnerability you want to validate.
  3. When the Vulnerability Validator window opens, replay the attack.
    1. Select an attack type and then click Replay Attack.
    2. In the Vulnerability Validator window, use the tabs at the top to switch between the steps in the attack traffic that occurred.
    3. On each tab, click Send to validate each attack with the Request Builder. The response headers and response body will return with the attack information.

Test remediation by re-running a scan

Validation scans use the scan engine. To test a fix on a single vulnerability without scanning, you can Replay an Attack.

Validate vulnerabilities

Run Validate Vulns to check the status of vulnerabilities previously discovered in scans that have been remediated. If the scan doesn’t find it, the vulnerability status changes to Remediated.

  1. In your app, select the scan that you want to validate.
  2. In the Vulnerabilities tab, select the vulnerabilities that you want to run a validation scan on.
  3. Click Validate Vulns. If you want to validate all vulnerabilities, simply click Validate Vulns.
  4. To view scan progress, click Validation History.
  5. When the scan completes, on the Vulnerabilities table, you can review the results in the Status column.
  6. On the Vulnerabilities page, verify that the vulnerability is not listed.
  7. To see any validation crawl logs and scan logs, see the Validation History tab.
Scanning recommendation

Use Validate Vulns to test for remediation for a complete view of your app security. Validation scans run against the attack findings from the parent scan will attempt to only find vulnerabilities that were discovered in the parent scan. A validation scan is not as comprehensive as running a full scan on the parent scan. Validation scans can only be run against a parent scan and cannot be run against an existing validation scan.