Antivirus For Mac 2017Application · Trendmicro

CVE-2018-15367

HIGH · 7.8 CVSS v3.0 Published 2018-10-23
Fix available
A fix is available. Upgrade to after 9.0.1356 or later.
See remediation →
80/100
Remediation priority · High
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
A ctl_set KERedirect Untrusted Pointer Dereference 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 · high confidence

A privilege escalation vulnerability in Trend Micro Antivirus for Mac versions 7.0 (2017) and above exists in the ctl_set KERedirect function due to untrusted pointer dereference. An attacker who has already obtained the ability to execute low-privileged code on the target system can exploit this flaw to gain elevated (administrator/root) privileges.

MitigationApply the latest security patch or update for Trend Micro Antivirus for Mac from the vendor. Until patched, minimize the risk by restricting local code execution privileges and monitoring for suspicious activity.

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
Antivirus For Mac 2017Application
Affected:>= 7.0, <= 7.1.1124
Antivirus For Mac 2018Application
Affected:>= 8.0, <= 8.0.3082
Antivirus For Mac 2019Application
Affected:>= 9.0, <= 9.0.1356

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Trend Micro Antivirus for Mac is installed
    Check the /Applications folder for the application, or use the command 'ls /Applications' to list installed applications and look for Trend Micro security products
    Affected if The Trend Micro Antivirus for Mac application is present in the system
  2. Identify the installed version number
    Right-click the Trend Micro Antivirus application, select Get Info, and view the Version field. Alternatively, run: defaults read /Applications/Trend\ Micro\ Antivirus.app/Contents/Info CFBundleVersion
    Affected if A version number is returned that falls within the affected ranges
  3. Compare version against affected ranges
    Review the installed version against these ranges: 7.0 to 7.1.1124 (2017), 8.0 to 8.0.3082 (2018), or 9.0 to 9.0.1356 (2019)
    Affected if The installed version is greater than or equal to 7.0 and less than or equal to 7.1.1124, OR greater than or equal to 8.0 and less than or equal to 8.0.3082, OR greater than or equal to 9.0 and less than or equal to 9.0.1356
  4. Assess if attacker already has code execution
    Review system logs and running processes for signs of unauthorized low-privileged code execution, as this vulnerability requires the attacker to already have the ability to run code on the system
    Affected if Any unexpected or unauthorized processes are running under standard user privileges

The environment is affected if Trend Micro Antivirus for Mac is installed with version 7.0-7.1.1124, 8.0-8.0.3082, or 9.0-9.0.1356 AND an attacker has already obtained low-privileged code execution capability on the system.

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 9.0.1356
Interim mitigation

Apply the latest security patch or update for Trend Micro Antivirus for Mac from the vendor. Until patched, minimize the risk by restricting local code execution privileges and monitoring for suspicious activity.

Fix this in Antivirus For Mac 2017 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-15367 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