ScanSuite
  • Introduction
  • Architecture
  • Installation
    • Technical Requirements
    • Install ScanSuite server
    • Set up DefectDojo
    • Troubleshooting
    • SSL/TLS Setup
  • Administration
    • Setup parameters and services
    • Configuring API keys for external systems
    • User administration
    • Security logs
  • Usage
    • Products
    • Performing a static code analysis
      • Git repository authentication
      • Scheduling Periodic and Incremental Scans
      • (Optional) Compiling the code
      • Executing the OpenAI scan
    • Managing scan execution
    • Working with scan results
      • Checking for exploitable vulnerabilities
      • Export to Securitm
      • (Optional) Parsing CSV exports
    • Performing dynamic web scanning
      • Authenticated scans
      • API scans
    • Running infrastructure tests
    • Scheduling the scan
    • Creating own scanning rules
  • Versions History
    • v 1.0
    • v 1.1
    • v 1.2
Powered by GitBook
On this page
  1. Usage
  2. Working with scan results

Checking for exploitable vulnerabilities

PreviousWorking with scan resultsNextExport to Securitm

Last updated 7 months ago

The database of exploitable vulnerabilities (existence of public exploit was confirmed or it was used during malware campaigns) is provided via Vuln DB menu:

It supports full text search by all fields and allows to quickly check whatever certain CVE is exploitable or which exploitable vulnerabilities existing for certain product.

On the top of that the results of Infrastructure (OpenVAS, Nessus, Nuclei) scans and code dependency checks (Trivy) are enriched by the info from this database. To view the enriched reports, download the ZIP archive via Scan History view by clicking on the Report button:

Then look for XLSX files, such as trivy-dep-report.xslx:

Or the similar Nessus, OpenVAS, Nuclei report within the respective folder:

Exploit availability is reflected via "Exploit" column: