Skip to content
Fencer Intel
critical 9.8

CVE-2017-14094 in the critical feed json

A vulnerability in Trend Micro Smart Protection Server (Standalone) versions 3.2 and below could allow an attacker to perform remote comman…

published 8y ago modified 4mo ago also EUVD-2017-5606

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
19.4%
EPSS 19.4% chance of exploitation in 30 days, percentile 97%
public exploits
1
Exploit-DB

Summary

A vulnerability in Trend Micro Smart Protection Server (Standalone) versions 3.2 and below could allow an attacker to perform remote command execution via a cron job injection on a vulnerable system.

Is CVE-2017-14094 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

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

Exploit prediction

19.37% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-43388 Trend Micro Smart Protection Server - Session Hijacking / Log File Disclosure / Remote Command Execution / Cron Job Injection / Local File Inclusion / Stored Cross-Site Scripting / Improper Access Control remote, 2017-12-19
  • coresecurity.com https://www.coresecurity.com/advisories/trend-micro-smart-protection-server-multiple-vulnerabilities referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

  • Trend Micro Trend Micro Smart Protection Server (Standalone)

Classification

Weakness
  • CWE-78 Improper Neutralization of Special Elements used in an OS Command
  • CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component

References

Sources

Fencer Intel 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.