dbcve.org
Antivirus\+ Security 2020Application · Trendmicro

CVE-2019-18190

CRITICAL · 9.8 CVSS v3.1 Published 2019-12-09
Fix available
A fix is available. Upgrade to 16.0.1227 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Trend Micro Security (Consumer) 2020 (v16.x) is affected by a vulnerability in where null pointer dereference errors result in the crash of application, which could potentially lead to possible unsigned code execution under certain circumstances.

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 null pointer dereference vulnerability in Trend Micro Security (Consumer) 2020 v16.x that causes application crashes and could potentially be leveraged for unsigned code execution under specific conditions. The vulnerability affects a security product designed to protect endpoints, creating a ironic situation where the protector becomes the attack vector.

MitigationApply the vendor-supplied patch or update to Trend Micro Security 2020 to the latest available version. If no patch is available, consider compensating controls such as restricting user interactions with the software or implementing additional endpoint monitoring.

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\+ Security 2020Application
Affected:>= 16.0, < 16.0.1227
Internet Security 2020Application
Affected:>= 16.0, < 16.0.1227
Maximum Security 2020Application
Affected:>= 16.0, < 16.0.1227
Premium Security 2020Application
Affected:>= 16.0, < 16.0.1227

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify installed Trend Micro Security 2020 product
    Open Windows Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell, and look for Trend Micro Security 2020, Antivirus+ Security 2020, Internet Security 2020, Maximum Security 2020, or Premium Security 2020
    Affected if Any of these products are listed in installed programs
  2. Determine installed version number
    Check the product version in Programs and Features under the 'Version' column, or inspect the registry key HKLM\SOFTWARE\TrendMicro\Deep Security Endpoint for the Agent version, or right-click the Trend Micro icon in the system tray and select 'About'
    Affected if Version cannot be determined or is not visible in the product UI
  3. Compare version against vulnerable range
    Compare the installed version to the affected range: 16.0.0 through 16.0.1226 are vulnerable; version 16.0.1227 and later are patched
    Affected if Installed version is 16.0.0 through 16.0.1226 (greater than or equal to 16.0 but less than 16.0.1227)
  4. Confirm the vulnerability trigger condition
    This is a null pointer dereference in the security product that can be triggered during normal operation when processing certain inputs; no specific user configuration is required for the product to be affected
    Affected if The vulnerable product version is running and the product's core scanning/protection features are enabled

A user is affected if Trend Micro Security 2020 (any consumer variant) is installed with a version between 16.0.0 and 16.0.1226 inclusive.

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.

dbcve · scoped
Upgrade available Upgrade to 16.0.1227 or later
Fixed in 16.0.1227
Interim mitigation

Apply the vendor-supplied patch or update to Trend Micro Security 2020 to the latest available version. If no patch is available, consider compensating controls such as restricting user interactions with the software or implementing additional endpoint monitoring.

Recommended fix High confidence

Trend Micro Security 2020 version 16.0.1227 or later

  1. Open the Trend Micro Security application on your system
  2. Navigate to Help > About to verify the current version (should show v16.x < 16.0.1227)
  3. Click on 'Check for Updates' or navigate to the Update section in the main interface
  4. Allow the application to download and install the latest version
  5. Restart the computer if prompted
  6. Verify the version after update by returning to Help > About and confirm the version is 16.0.1227 or later
  7. Alternatively, download the latest installer directly from esupport.trendmicro.com if automatic update is not available

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Antivirus\+ Security 2020 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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