CVE-2018-15366
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 UrlfWTPPagePtr KERedirect Use-After-Free Privilege Escalation vulnerability in Trend Micro Antivirus for Mac (Consumer) 7.0 (2017) and above could allow a local attacker to escalate privileges on vulnerable installations. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability.
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 confidenceA use-after-free vulnerability in the UrlfWTPPagePtr KERedirect component of Trend Micro Antivirus for Mac allows local attackers to escalate privileges by freeing memory and then accessing it after it has been deallocated. The attacker must first achieve low-privileged code execution on the target system before exploiting this vulnerability.
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>= 7.0, <= 7.1.1124>= 8.0, <= 8.0.3082>= 9.0, <= 9.0.1356CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/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.
-
Check if Trend Micro Antivirus for Mac is installedLook for the product in Applications folder or check system for installed security software. On macOS, you can use: ls /Applications | grep -i 'trend micro' or system_profiler SPApplicationsDataTypeAffected if The product is not present on the system, the user is not affected.
-
Identify the installed version of Trend Micro Antivirus for MacOpen the application, go to About or Preferences to find the version number. Alternatively, check the application bundle info: defaults read /Applications/TrendMicroSecurityAgent.app/Contents/Info CFBundleShortVersionString 2>/dev/null or look at the app's Info.plistAffected if Unable to determine version - further investigation needed.
-
Compare installed version against CVE-2018-15366 affected rangesFor version 2017 releases: check if version is >= 7.0 and <= 7.1.1124. For version 2018 releases: check if version is >= 8.0 and <= 8.0.3082. For version 2019 releases: check if version is >= 9.0 and <= 9.0.1356Affected if Installed version falls within any of these ranges: 7.0-7.1.1124, 8.0-8.0.3082, or 9.0-9.0.1356 - the system is potentially affected.
-
Verify the KERedirect component is presentThis is a kernel extension component. Check for presence of related kernel extensions: kextstat | grep -i trend or ls /Library/Extensions/ | grep -i trendAffected if The vulnerable component is loaded as part of the security product, required for exploitation.
-
Confirm local low-privileged access existsReview user accounts on the system. The CVE requires the attacker to first achieve low-privileged code execution. Check for unnecessary user accounts or shared credentialsAffected if Multiple users with varying privilege levels exist, especially untrusted accounts - increases exploitability but does not change affected status if product version is vulnerable.
The system is affected if Trend Micro Antivirus for Mac is installed AND the installed version falls within 7.0-7.1.1124, 8.0-8.0.3082, or 9.0-9.0.1356.
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-provided patches or updates for Trend Micro Antivirus for Mac 7.0 and later versions. Until a patch is available, minimize the risk by restricting local access and ensuring principle of least privilege for all user accounts.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15366 — 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-15366 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