CVE-2019-7478
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 GMS allow unauthenticated user to SQL injection in Webservice module. This vulnerability affected GMS versions GMS 8.4, 8.5, 8.6, 8.7, 9.0 and 9.1.
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 confidenceAn unauthenticated SQL injection vulnerability in the GMS Webservice module allows remote attackers to inject malicious SQL queries without any authentication. This critical flaw (CVSS 9.8) affects GMS versions 8.4 through 9.1 and could enable full database compromise, data exfiltration, or potentially remote code execution depending on database configuration.
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.4= 8.5= 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Sonicwall GMS is installedLocate GMS installation directories or check system inventory for Sonicwall Global Management System softwareAffected if GMS software is found on the system
-
Check installed GMS versionUse system inventory tools, package manager, or GMS admin interface to determine the exact version numberAffected if Installed version matches 8.4, 8.5, 8.6, 8.7, 9.0, or 9.1
-
Verify Webservice module statusExamine GMS configuration files or admin interface to confirm whether the Webservice module is enabled and accessibleAffected if Webservice module is enabled and exposed to network
-
Assess network exposure of Webservice interfaceReview firewall rules, network access controls, or reverse proxy configuration to determine if GMS Webservice port is reachable from external networksAffected if Webservice module is reachable from untrusted networks without authentication
Environment is affected if Sonicwall GMS versions 8.4 through 9.1 are installed with the Webservice module enabled and exposed to network 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.
dbcve · scopedUpgrade to a patched GMS version if available; otherwise deploy WAF rules to filter SQL injection payloads and restrict external access to the Webservice module until a fix can be applied.
GMS 9.2 or later
- Identify the current GMS version running in your environment
- Download the latest GMS version (9.2 or later) from the official SonicWall support portal
- Review release notes for any migration or upgrade prerequisites
- Back up the current GMS configuration and database
- Stop the GMS services before upgrading
- Install the updated GMS version following the official upgrade documentation
- Restart GMS services and verify the application is functioning normally
- Confirm the Webservice module is operational and the SQL injection vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7478 — 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-7478 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