Skip to content
Fencer Vulns
high 7.8

CVE-2019-9491 in the critical feed json

Trend Micro Anti-Threat Toolkit (ATTK) versions 1.62.0.1218 and below have a vulnerability that may allow an attacker to place malicious fi…

published 2019-10-21 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-18865

cvss
7.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
12.9%
EPSS 12.9% chance of exploitation in 30 days, percentile 96%
public exploits
1
Exploit-DB

Summary

Trend Micro Anti-Threat Toolkit (ATTK) versions 1.62.0.1218 and below have a vulnerability that may allow an attacker to place malicious files in the same directory, potentially leading to arbitrary remote code execution (RCE) when executed.

Timeline

  1. First public exploit (EDB-47527)
  2. Published

Exploit prediction

12.94% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-47527 Trend Micro Anti-Threat Toolkit 1.62.0.1218 - Remote Code Execution local, 2019-10-21
  • seclists.org https://seclists.org/bugtraq/2019/Oct/30 referenced PoC, tagged "exploit" by a source, unverified
  • seclists.org http://seclists.org/fulldisclosure/2019/Oct/42 referenced PoC, tagged "exploit" by a source, unverified
  • seclists.org https://seclists.org/bugtraq/2020/Jan/55 referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/156160/TrendMicro-Anti-Threat-Toolkit-Improper-Fix.html referenced PoC, tagged "exploit" by a source, unverified
  • seclists.org http://seclists.org/fulldisclosure/2020/Jan/50 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 5.1 AV:N/AC:H/Au:N/C:P/I:P/A:P

Affected products

  • Trend Micro Trend Micro Anti-Threat Toolkit (ATTK)

Classification

Weakness
  • CWE-427 Uncontrolled Search Path Element

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.