dbcve.org
Endpoint ProtectionApplication · Symantec

CVE-2018-18366

MEDIUM · 6.5 CVSS v3.0 Published 2019-04-25
Fix available
A fix is available. Upgrade to 3.00.31.2817 / 22.16.3 or later.
See remediation →
67/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
Symantec Norton Security prior to 22.16.3, SEP (Windows client) prior to and including 12.1 RU6 MP9, and prior to 14.2 RU1, SEP SBE prior to Cloud Agent 3.00.31.2817, NIS-22.15.2.22, SEP-12.1.7484.7002 and SEP Cloud prior to 22.16.3 may be susceptible to a kernel memory disclosure, which is a type of issue where a specially crafted IRP request can cause the driver to return uninitialized memory.

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 confidence

A kernel memory disclosure vulnerability exists in multiple Symantec/Norton security products where specially crafted IRP (I/O Request Packet) requests cause the driver to return uninitialized memory to user space. This information disclosure could potentially be leveraged for further exploitation, including kernel memory layout revelation or privilege escalation.

MitigationUpdate affected Symantec/Norton products to the patched versions: Norton Security to 22.16.3 or later, SEP (Windows client) to 14.2 RU1 or later, SEP SBE to Cloud Agent 3.00.31.2817 or later, and SEP Cloud to 22.16.3 or later.

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
Endpoint ProtectionApplication
Affected:= 11.0= 12.1= 14= 14.0.0= 14.0.1= 14.2= nis-22.15.2.22= sep-12.1.7484.7002
Endpoint Protection CloudApplication
Affected:< 22.16.3
Endpoint Protection Cloud AgentApplication
Affected:< 3.00.31.2817
Norton SecurityApplication
Affected:< 22.16.3

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
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/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 Norton or Symantec product
    Open Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | DisplayName' in PowerShell to list installed software. Look for entries containing 'Norton' or 'Symantec Endpoint Protection'.
    Affected if A Norton or Symantec security product is listed with a version that matches the affected version ranges.
  2. Confirm product name and exact version
    Right-click the installed product in Programs and Features and select Properties, or use 'Get-ItemProperty' on the specific registry key for the product to retrieve the exact version number (Version field).
    Affected if The version matches any of: 11.0, 12.1, 14, 14.0.0, 14.0.1, 14.2, nis-22.15.2.22, sep-12.1.7484.7002, or any version prior to 22.16.3 for Cloud/Norton, or prior to 3.00.31.2817 for Cloud Agent.
  3. Check for running Symantec/Norton driver processes
    Open Task Manager or run 'Get-Process | Where-Object {$_.Company -match "Norton|Symantec"}' in PowerShell to see if the security product's driver services are active.
    Affected if The product's driver processes are running on the system.
  4. Verify driver file presence (optional validation)
    Check the Windows\System32\drivers folder for common Symantec/Norton driver files. Use 'Get-ChildItem C:\Windows\System32\drivers | Where-Object {$_.Name -like "*sym*" -or $_.Name -like "*nort*"}' to list potential driver files.
    Affected if Symantec or Norton kernel drivers are present on the system.

You are affected if a Norton or Symantec Endpoint Protection product is installed with a version matching the affected ranges (11.0, 12.1, 14.x, or versions prior to 22.16.3 for Norton/Cloud, or prior to 3.00.31.2817 for Cloud Agent).

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 3.00.31.2817 / 22.16.3 or later
Fixed in 3.00.31.281722.16.3
Interim mitigation

Update affected Symantec/Norton products to the patched versions: Norton Security to 22.16.3 or later, SEP (Windows client) to 14.2 RU1 or later, SEP SBE to Cloud Agent 3.00.31.2817 or later, and SEP Cloud to 22.16.3 or later.

Fix this in Endpoint Protection Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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