CVE-2018-18367
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 · uneditedSymantec Endpoint Protection Manager (SEPM) prior to and including 12.1 RU6 MP9 and prior to 14.2 RU1 may be susceptible to a DLL Preloading vulnerability, which is a type of issue that can occur when an application looks to call a DLL for execution and an attacker provides a malicious DLL to use instead.
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 confidenceSymantec Endpoint Protection Manager (SEPM) versions prior to 14.2 RU1 and 12.1 RU6 MP9 and earlier contain a DLL Preloading vulnerability where the application may load a malicious DLL file instead of the intended legitimate DLL, potentially allowing arbitrary code execution.
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= 12.1= 14= 14.0.1= 14.1= 14.2CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 SEPM installation locationLocate the Symantec Endpoint Protection Manager installation directory, typically found under C:\Program Files\Symantec\Symantec Endpoint Protection Manager or C:\Program Files (x86)\Symantec\Symantec Endpoint Protection ManagerAffected if SEPM is installed on the system
-
Find installed SEPM versionCheck the version of the SEPM executable or check the Windows Programs and Features list for the installed version of Symantec Endpoint Protection ManagerAffected if The version shown is 12.1 (any build), 14, 14.0.1, 14.1, or 14.2 without the RU1 update
-
Compare version to affected rangeVerify the exact version number against the affected range: versions prior to 14.2 RU1 and versions prior to 12.1 RU6 MP9 are vulnerableAffected if The installed version is 14.2 (without RU1) or 12.1 RU6 MP9 or earlier, or any version 14, 14.0.1, or 14.1
-
Confirm SEPM is runningVerify the Symantec Endpoint Protection Manager service or application is actively running on the hostAffected if SEPM service is installed and running on the system
The system is affected if Symantec Endpoint Protection Manager is installed and the version is 12.1 RU6 MP9 or earlier, or any version 14, 14.0.1, 14.1, or 14.2 prior to RU1.
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 dataUpdate SEPM to version 14.2 RU1 or later, or 12.1 RU6 MP10 or later. As a compensating control, ensure the application runs from trusted directories and implement secure DLL search order settings to prevent loading from untrusted paths.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-18367 — 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-2018-18367 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