Free Shipping On Many Orders Over $350 (Exclusion Apply)

Chat To Us - 7am-10pm - 7 Days A Week

SonicWall SSL-VPN Misconfiguration Leads To Possible Domain Name (DNS) Collision Vulnerability

The Tech Geeks |


There exists a potential domain name collision vulnerability in SonicWall SSL-VPN technology that could result from a security misconfiguration of the impacted products.

SonicWall is not aware that the reported vulnerability has been exploited or that any customer has been negatively impacted by the vulnerability.

A domain name collision occurs when an attempt to resolve a name used in a private namespace (e.g., under a non-delegated top-level domain, or a short, unqualified name) results in a query to the public Domain Name System (DNS). When the administrative boundaries of private and public namespaces overlap, name resolution may yield unintended or harmful results.

 EXAMPLE: If the organization’s internal domain has a valid top-level domain and is not already publicly registered, an attacker can register the domain publicly, and use the public domain to receive DNS requests that were intended for the internal domain. This gives an attacker the ability to poison the organization’s DNS requests and remotely capture hashes from the organization.

The web interface for SonicWall SSL-VPN products (which include SonicWall SMA100 series, SMA1000 series and the SSL-VPN feature on SonicWall firewalls) has the option to publicly display their organization’s internal domain names in the ‘Domain’ drop-down menu.

An attacker with knowledge of an organization’s internal domain name can potentially take advantage of a domain name collision vulnerability.


Organizations with SonicWall SMA 100 and SMA 1000  series appliances, as well as any firewall products, including TZ, NSa, NSA, NSv, SuperMassive and NSsp series with SSL-VPN enabled, should immediately implement the following steps based on products deployed:

SonicWall SMA 100 series

  • Configure the domain names different from the AD/LDAP names and existing internal domain names.
  • Hide the SMA domain list by enabling the Hide Domain list on portal login page in SMA 100 portal settings.

SonicWall SMA 1000 series

  • For Microsoft Active Directory (Advanced) authentication servers, ensure that the option labeled ‘Users can choose from a list of domains’ is not selected. This is the default configuration.

SonicWall Firewalls (SSL-VPN Server Settings)

  • Do not show entire internal domain name in the ‘User Domain’ field

    Generation 7

    Generation 5 & 6

    The mitigation is not to put internal fully qualified domain names (FQDN), such as ‘,’ into the ‘User Domain’ field (see above). Instead, users can use a generic name such as ‘LocalDomain1,’ which can’t be resolved by DNS server.