CVE-2019-19693
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 · uneditedThe Trend Micro Security 2020 consumer family of products contains a vulnerability that could allow a local attacker to disclose sensitive information or to create a denial-of-service condition on affected 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 confidenceTrend Micro Security 2020 consumer products contain a local vulnerability exploitable by an attacker with low-privileged code execution, allowing disclosure of sensitive information or denial-of-service. The attack requires local access rather than remote exploitation.
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>= 16.0, < 16.0.1249>= 16.0, < 16.0.1249>= 16.0, < 16.0.1249>= 16.0, < 16.0.1249CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed Trend Micro Security 2020 productOpen Programs and Features (appwiz.cpl) or use a software inventory tool to list installed security software. Look for Trendmicro Antivirus+ Security 2020, Trendmicro Internet Security 2020, Trendmicro Maximum Security 2020, or Trendmicro Premium Security 2020.Affected if Any of these four Trend Micro 2020 consumer products are listed as installed.
-
Determine the installed product versionRight-click the installed Trend Micro product in Programs and Features and select Properties, or check the program's About/Help section. Note the exact version number displayed (format is typically 16.0.xxxx).Affected if A version number is displayed in the format 16.0.xxxx.
-
Compare version against vulnerable rangeCompare the installed version number to the affected range: versions 16.0.0 through 16.0.1248 are vulnerable. Version 16.0.1249 and later are patched.Affected if The installed version is 16.0.1248 or lower (16.0.xxxx where xxxx is less than 1249).
The system is affected if a Trend Micro Security 2020 consumer product (Antivirus+, Internet Security, Maximum Security, or Premium Security) is installed with a version between 16.0.0 and 16.0.1248 inclusive.
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 data16.0.1249
Apply the vendor-supplied security update or patch from Trend Micro for the affected Security 2020 product version. Ensure the antivirus software is updated to the latest patched release.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2019-19693 — 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-2019-19693 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