dbcve.org
SonicosvOperating system · Sonicwall

CVE-2019-7475

CRITICAL · 9.8 CVSS v3.1 Published 2019-04-02
Fix available
A fix is available. Upgrade to after 5.9.1.10 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability in SonicWall SonicOS and SonicOSv with management enabled system on specific configuration allow unprivileged user to access advanced routing services. This vulnerability affected SonicOS Gen 5 version 5.9.1.10 and earlier, Gen 6 version 6.2.7.3, 6.5.1.3, 6.5.2.2, 6.5.3.1, 6.2.7.8, 6.4.0.0, 6.5.1.8, 6.0.5.3-86o and SonicOSv 6.5.0.2-8v_RC363 (VMWARE), 6.5.0.2.8v_RC367 (AZURE), SonicOSv 6.5.0.2.8v_RC368 (AWS), SonicOSv 6.5.0.2.8v_RC366 (HYPER_V).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A critical vulnerability in SonicWall SonicOS and SonicOSv allows unprivileged users to access advanced routing services when management is enabled on specific configurations. This affects multiple Generation 5 and Generation 6 firmware versions as well as SonicOSv across VMware, Azure, AWS, and Hyper-V platforms.

MitigationUpdate to patched SonicOS versions or disable management access for unprivileged users on affected configurations. Refer to SonicWall advisory for specific patched version numbers.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SonicosvOperating system
Affected:= 6.5.0.2-8v_rc363= 6.5.0.2.8v_rc366= 6.5.0.2.8v_rc367= 6.5.0.2.8v_rc368
SonicosOperating system
Affected:<= 5.9.1.10= 6.0.5.3-86o= 6.2.7.3= 6.2.7.8= 6.4.0.0= 6.5.1.3= 6.5.1.8= 6.5.2.2= 6.5.3.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SonicOS or SonicOSv version
    Access the SonicWall device CLI or web management interface. In the CLI, run 'show version' or 'get system info'. In the web UI, navigate to System > Status to view the firmware version.
    Affected if The installed version matches one of the affected versions: SonicOSv 6.5.0.2-8v_rc363, 6.5.0.2.8v_rc366, 6.5.0.2.8v_rc367, 6.5.0.2.8v_rc368; or SonicOS <= 5.9.1.10, 6.0.5.3-86o, 6.2.7.3, 6.2.7.8, 6.4.0.0, 6.5.1.3, 6.5.1.8, 6.5.2.2, or 6.5.3.1.
  2. Confirm management interface is enabled
    In the SonicWall web UI, go to Users > Settings or System > Administration to verify if HTTP/HTTPS management access is enabled. In CLI, check 'show interface' for management zone configurations.
    Affected if Management access is enabled on any interface (LAN, WAN, or dedicated management). The vulnerability specifically requires management to be accessible for unprivileged users to exploit it.
  3. Check for unprivileged user accounts
    In the SonicWall web UI, navigate to Users > Local Users or Users > Administrators to review defined user accounts and their privilege levels.
    Affected if Non-administrative or low-privilege user accounts exist on the system. The vulnerability allows these unprivileged users to access advanced routing services.
  4. Verify advanced routing services are accessible
    Review the routing configuration and policy settings. Check if features like static routes, OSPF, BGP, or VRRP are configured and accessible through the management interface without elevated privileges.
    Affected if Advanced routing services can be viewed or modified by users without administrator privileges.

You are affected if your SonicOS or SonicOSv version matches the listed affected versions AND management interface is enabled with unprivileged user accounts present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 5.9.1.10
Interim mitigation

Update to patched SonicOS versions or disable management access for unprivileged users on affected configurations. Refer to SonicWall advisory for specific patched version numbers.

Fix this in Sonicosv Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-7475 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-7475 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data