CVE-2019-7476
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 · uneditedA vulnerability in SonicWall Global Management System (GMS), allow a remote user to gain access to the appliance using existing SSH key. This vulnerability affects GMS versions 9.1, 9.0, 8.7, 8.6, 8.4, 8.3 and earlier.
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 · moderate confidenceA pre-authentication vulnerability in SonicWall Global Management System (GMS) allows remote attackers to gain unauthorized access to the appliance by exploiting an existing SSH key. This affects versions 9.1, 9.0, 8.7, 8.6, 8.3 and earlier, enabling remote code execution or system compromise without valid credentials.
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<= 8.3= 8.4= 8.6= 8.7= 9.0= 9.1CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if SonicWall GMS is installedLocate and inspect the GMS installation directory or check running services for 'GMS' or 'sonicwall' processesAffected if The system is running SonicWall Global Management System software
-
Check the installed GMS versionRun 'sonicwall_gms -version' or check the About/Version page in the GMS web interfaceAffected if The version is 8.3 or earlier, or exactly 8.4, 8.6, 8.7, 9.0, or 9.1
-
Verify if SSH service is enabled on the GMS applianceCheck if port 22 (SSH) is listening on the appliance using 'netstat -an | grep :22' or 'nmap -p 22 <appliance_ip>'Affected if SSH is exposed and listening on the appliance
-
Inspect for the presence of default or hardcoded SSH keysCheck the SSH authorized_keys file, typically in /home/<user>/.ssh/ or the GMS configuration directory for any pre-existing SSH keysAffected if A pre-configured SSH key exists in the system that was not explicitly added by the administrator
-
Review SSH access logs for unauthorized connection attemptsExamine /var/log/secure or SSH daemon logs for connections from untrusted sources before any patching was performedAffected if The appliance SSH was externally accessible and shows connection activity from untrusted networks
A user is affected if they are running SonicWall GMS versions 8.3 or earlier, 8.4, 8.6, 8.7, 9.0, or 9.1 with SSH enabled and exposed to networks where attackers could use an existing SSH key to gain pre-authentication access.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade GMS to the latest patched version and immediately rotate/revoke all existing SSH keys used for appliance access. Restrict SSH access to trusted networks and implement key-based authentication with proper key management.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7476 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-7476 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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