Skip to content

Scanning Engine v2 - Module - SonicWall

Overview

Targeting

Schemas

The schema for the body object of all results generated with .task.module_name equal to sonicwall can be found here. The schema for results is available both in standalone and bundled form.

Examples

These are examples of the .body object for results with .task.module_name equal to sonicwall.

Live Host

This example was generated with a live host on the internet.

{
  "name": "SonicWall Administrator",
  "url": "https://[REDACTED]:443/",
  "evidence": "<meta name=\"SonicWall Administrator\" content=\"Copyright 2004 (c) SonicWall, Inc. All rights reserved.\">",
  "redirects": [],
  "vulnerabilities": [
    "CVE-2022-22274",
    "CVE-2023-0656"
  ]
}

Changelog

v1.2.0 (2026-04-30)

  • Reverted all changes made as part of v1.1.0, underwriting requires that SSLVPN modules always check everything and ignore failures.
  • Added new path on which to check for SonicWall.

v1.1.0 (2026-03-18)

  • Rework the scanning logic:
  • Access each target sequentially, not in parallel
  • Stop talking to a target if any TCP or TLS errors occur
  • Stop talking to a target if any endpoint identifies the target as a SonicWall
  • Reorder the endpoints by success rate, and add a new endpoint

v1.0.0 (2025-05-05)

  • Initial release of versioning for each module. All modules are being tagged with version number 1.0.0. Going forward:
  • Major version should be changed when there are changes that impact consumers or clients of the modules.
  • Minor version should be changed when there are additions which enrich or enhance the module but shouldn't affect consumers or clients.
  • Patch version should be changed when there are bugfixes.