SonicosvOperating system · Sonicwall
CVE-2019-7474
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 SonicOS and SonicOSv, allow authenticated read-only admin to leave the firewall in an unstable state by downloading certificate with specific extension. 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 confidenceA vulnerability in SonicWall SonicOS and SonicOSv allows an authenticated read-only administrator to place the firewall in an unstable state by downloading a certificate file with a specific extension. The issue stems from improper handling of certificate file extensions in the firmware, causing a denial-of-service condition that leaves the firewall in a non-functional state.
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
= 6.5.0.2-8v_rc363= 6.5.0.2.8v_rc366= 6.5.0.2.8v_rc367= 6.5.0.2.8v_rc368<= 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.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 installed SonicOS versionLog into the SonicWall management interface and navigate to System > Status, or run 'show version' via CLI. Note the exact firmware version displayed.Affected if The version matches one of the affected versions listed: 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.
-
Check for read-only administrator accountsNavigate to Manage > Users > Local Users & Groups (or Users > Settings > Local Users in older versions). Review the list of defined admin accounts and identify any with 'Read Only' privilege level.Affected if Any read-only administrator account exists in the system.
-
Verify certificate management accessibility for read-only adminsLog in using a read-only administrator account. Navigate to Device > Certificates (or System > Certificates) and attempt to access the certificate download or import functions. Observe whether the interface allows certificate-related actions.Affected if The read-only admin account can access or trigger certificate download/import features.
-
Inspect system state after certificate operationIf a read-only admin can access certificate functions, check System > Diagnostics or the dashboard for any error messages, service status indicators, or system health warnings indicating the firewall has entered an unstable or non-functional state.Affected if The firewall shows degraded status, unavailable services, or requires reboot after certificate file operations.
You are affected if your SonicOS or SonicOSv version matches the affected list AND a read-only administrator account can access certificate management features, leading to denial-of-service.
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 SonicWall SonicOS to version 6.5.4.0 or later for Gen 6, and apply appropriate patches for Gen 5 as specified in SonicWall advisory. Consider restricting read-only admin privileges and implementing certificate upload validation until patches are applied.
Fix this in Sonicosv
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7474 — 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-7474 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