dbcve.org
SonicosvOperating system · Sonicwall

CVE-2018-9867

MEDIUM · 5.5 CVSS v3.1 Published 2019-02-19
Fix available
A fix is available. Upgrade to after 5.9.1.10 or later.
See remediation →
57/100
Remediation priority · Elevated
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
In SonicWall SonicOS, administrators without full permissions can download imported certificates. Occurs when administrators who are not in the SonicWall Administrators user group attempt to download imported certificates. 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

In SonicWall SonicOS, an access control bypass exists where administrators who are NOT members of the SonicWall Administrators user group can download imported certificates, despite lacking full permissions. This is a privilege escalation vulnerability in the certificate management functionality affecting multiple Gen 5 and Gen 6 versions.

MitigationApply vendor-supplied patches by upgrading to fixed SonicOS versions. Ensure administrator accounts are properly assigned to the SonicWall Administrators group for appropriate access control.

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.0.0.0, <= 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 installed SonicOS version
    Access the SonicWall management interface or use the device CLI command to display the firmware version (typically 'show version' or via the Dashboard > Device page in the web interface). Compare the displayed version number against the affected ranges: SonicOSv 6.5.0.2-8v_rc363 through 6.5.0.2.8v_rc368, SonicOS 5.0.0.0-5.9.1.10, or specific versions 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.
    Affected if The installed version matches one of the listed affected versions or falls within the affected ranges.
  2. Verify certificate import feature is in use
    Navigate to the SSL VPN or Certificates management section of the SonicWall interface (typically under Users > Settings or VPN > SSL VPN Settings). Check if any certificates have been imported onto the device.
    Affected if Imported certificates exist on the device, creating a target for the vulnerability.
  3. Review administrator account configurations
    Access the SonicWall administrator management section (typically under Administration > Administrators or Users > Local Users > Administrators). List all configured administrator accounts and identify which ones are NOT members of the SonicWall Administrators group.
    Affected if There exist administrator accounts that are not members of the SonicWall Administrators group.
  4. Test certificate download access for non-privileged admins
    Using an administrator account that is NOT a member of the SonicWall Administrators group, attempt to access the certificate download or export functionality for imported certificates. Observe whether the download completes successfully despite the restricted permissions.
    Affected if A non-SonicWall Administrators group member can successfully download imported certificates.

Your environment is affected if the SonicOS version matches an affected version, imported certificates exist on the device, and administrator accounts exist outside the SonicWall Administrators group who can download those certificates.

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

Apply vendor-supplied patches by upgrading to fixed SonicOS versions. Ensure administrator accounts are properly assigned to the SonicWall Administrators group for appropriate access control.

Fix this in Sonicosv Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-9867 — 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-2018-9867 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