dbcve.org
Antivirus \+ SecurityApplication · Trendmicro

CVE-2018-10514

HIGH · 7.8 CVSS v3.0 Published 2018-08-30
Fix available
A fix is available. Upgrade to after 12.0 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 Missing Impersonation Privilege Escalation vulnerability in Trend Micro Security 2018 (Consumer) products 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 the 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 confidence

This is a local privilege escalation vulnerability in Trend Micro Security 2018 Consumer products caused by missing impersonation privileges. An attacker with the ability to execute low-privileged code on the target system can exploit this flaw to gain elevated (administrative) privileges, effectively escalating from a standard user to system-level access.

MitigationApply the vendor patch from Trend Micro for Security 2018 Consumer products; ensure all installations are updated to the latest version through the product's built-in update mechanism or by downloading the patched version from Trend Micro's official support channels.

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 \+ SecurityApplication
Affected:<= 12.0
Internet SecurityApplication
Affected:<= 12.0
Maximum SecurityApplication
Affected:<= 12.0
Premium SecurityApplication
Affected:<= 12.0

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. List installed Trend Micro security products
    Open Windows Settings > Apps & Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select DisplayName, DisplayVersion | Where-Object {$_.DisplayName -like "*Trend*"}' in PowerShell to enumerate installed programs containing "Trend" in the name.
    Affected if any Trend Micro security product (Antivirus+Security, Internet Security, Maximum Security, or Premium Security) appears in the installed programs list
  2. Identify the specific Trend Micro product name
    From the installed programs list, note the exact product name: Trendmicro Antivirus + Security, Trendmicro Internet Security, Trendmicro Maximum Security, or Trendmicro Premium Security.
    Affected if product name matches one of the four affected consumer product lines
  3. Determine the installed version number
    Run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select DisplayName, DisplayVersion | Where-Object {$_.DisplayName -like "*Trend*"}' or check the product's About/Help > About section within the application to retrieve the precise version number.
    Affected if version number is readable and available for comparison
  4. Compare version against affected range
    Compare the installed version number to the affected threshold of 12.0. Versions 12.0 and below are affected; versions above 12.0 are not.
    Affected if installed version is 12.0 or lower (for example, 11.0, 10.0, or any 12.0.x release)

A system is affected if any of the four Trend Micro Security 2018 Consumer products (Antivirus+Security, Internet Security, Maximum Security, or Premium Security) is installed with version 12.0 or lower.

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

Apply the vendor patch from Trend Micro for Security 2018 Consumer products; ensure all installations are updated to the latest version through the product's built-in update mechanism or by downloading the patched version from Trend Micro's official support channels.

Fix this in Antivirus \+ Security Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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