CVE-2019-7479
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 SonicOS allow authenticated read-only admin can elevate permissions to configuration mode. This vulnerability affected SonicOS Gen 5 version 5.9.1.12-4o and earlier, Gen 6 version 6.2.7.4-32n, 6.5.1.4-4n, 6.5.2.3-4n, 6.5.3.3-3n, 6.2.7.10-3n, 6.4.1.0-3n, 6.5.3.3-3n, 6.5.1.9-4n 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 privilege escalation vulnerability in SonicOS allows authenticated read-only administrators to elevate their privileges to configuration mode, granting full administrative access to the firewall. This is a vertical privilege escalation where a limited admin account can access full administrative functions.
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<= 5.9.1.12-4o= 6.2.7.4-32n= 6.2.7.10-3n= 6.4.1.0-3n= 6.5.1.4-4n= 6.5.1.9-4n= 6.5.2.3-4n= 6.5.3.3-3n= 6.5.0.2.8vCVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 installed SonicOS versionLog into the SonicWall management interface and navigate to System > Status or use the CLI command 'show version' to display the firmware version. Note the full version string including the build number (e.g., 5.9.1.12-4o).Affected if The installed version is 5.9.1.12-4o or earlier, OR matches any of these specific builds: 6.2.7.4-32n, 6.2.7.10-3n, 6.4.1.0-3n, 6.5.1.4-4n, 6.5.1.9-4n, 6.5.2.3-4n, 6.5.3.3-3n, or 6.5.0.2.8v (Sonicosv).
-
Confirm product modelCheck the device model in System > Status or via 'show system info' CLI command to confirm whether the device runs SonicOS or SonicOSv (virtual appliance).Affected if The device runs SonicOS or SonicOSv with an affected version.
-
Review admin account configurationNavigate to Users > Local Users or use CLI 'show user local' to list all configured administrator accounts. Identify accounts with 'read-only' or 'monitor-only' privilege levels.Affected if One or more read-only or monitor-only administrator accounts exist on the device.
-
Audit for configuration mode accessReview system logs, audit logs, or administrative access logs for events where read-only accounts accessed configuration menus, changed settings, or performed privileged actions. Check under Logs > View or CLI 'show log' for entries indicating privilege escalation.Affected if Read-only administrator accounts have accessed configuration functions or performed administrative actions they should not be able to perform.
The environment is affected if the SonicOS/SonicOSv version matches any of the listed affected versions AND read-only administrator accounts exist on the device, as these accounts could have exploited the privilege escalation to gain full administrative 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 dataApply vendor-supplied firmware patches for all affected SonicOS versions as listed in the advisory. Implement least-privilege access controls and monitor administrative privilege escalation events.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7479 — 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-7479 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