Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2017-14095: Remote Command Execution via LFI in Trend Micro Smart Protection Server <= 3.2

Published Jan 19, 2018 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.1High · v3
EPSS12.5%96th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Trend Micro
IdentifiersCVE-2017-14095CWE-284

CVE-2017-14095 is a critical vulnerability in Trend Micro Smart Protection Server (Standalone) versions 3.2 and below. The flaw is an access control issue (CWE-284) that allows remote attackers to execute arbitrary commands on the affected system by exploiting a local file inclusion (LFI) vulnerability. The vulnerability does not require authentication, making it highly exploitable. The issue was discovered and reported by Core Security, and a public proof-of-concept exploit (EDB-ID 43388) is available.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote, unauthenticated attackers to execute arbitrary commands on the target system, leading to full compromise of confidentiality, integrity, and availability. Attackers can gain control over the server, exfiltrate data, deploy malware, or use the compromised system as a pivot point for further attacks.

Mitigation

If you can’t patch tonight, do this now.

Until a patch is available, restrict access to the Smart Protection Server to trusted networks only, monitor logs for suspicious activity, and consider deploying web application firewalls or other compensating controls to detect and block exploitation attempts. Regularly review vendor advisories for updates.

Remediation

Patch, then assume compromise.

No official patch or mitigation was available at the time of reporting. Administrators should check for any vendor updates or advisories and apply patches as soon as they become available. In the absence of a patch, consider restricting network access to the affected system and monitoring for signs of exploitation.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Trend MicroSmart Protection Serverapplication
FAQ

Frequently asked questions

Is CVE-2017-14095 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2017-14095 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2017-14095?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2017-14095.
Is there a patch for CVE-2017-14095?
No official patch or mitigation was available at the time of reporting. Administrators should check for any vendor updates or advisories and apply patches as soon as they become available.
What products are affected by CVE-2017-14095?
Trend Micro Smart Protection Server.
How severe is CVE-2017-14095?
CVE-2017-14095 has a CVSS v3 score of 8.1 (High) and an EPSS score of 12.5% (96th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.