CVE-2017-11394 in the critical feed json
Proxy command injection vulnerability in Trend Micro OfficeScan 11 and XG (12) allows remote attackers to execute arbitrary code on vulnera…
published 2017-08-03 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-3021
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 66.8%
- EPSS 66.8% chance of exploitation in 30 days, percentile 99.2%
- public exploits
- 2
- Metasploit, Exploit-DB
Summary
Proxy command injection vulnerability in Trend Micro OfficeScan 11 and XG (12) allows remote attackers to execute arbitrary code on vulnerable installations. The specific flaw can be exploited by parsing the T parameter within Proxy.php. Formerly ZDI-CAN-4544.
Patch / fix
Timeline
- Published
- First public exploit (Metasploit exploit/windows/http/trendmicro_officescan_widget_exec)
Exploit prediction
66.77% chance of exploitation in the next 30 days, higher than 99.2% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit exploit/windows/http/trendmicro_officescan_widget_exec Trend Micro OfficeScan Remote Code Execution metasploit exploit, excellent rank, 2017-10-07
- EDB-42971 Trend Micro OfficeScan 11.0/XG (12.0) - Remote Code Execution (Metasploit) webapps, 2017-10-11
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 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Affected products
- Trend Micro Trend Micro OfficeScan
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
success.trendmicro.com
/solution/1117769
mitigation, patch, vendor-advisory
-
exploit-db.com
/exploits/42971/
exploit
-
securityfocus.com
/bid/100130
vdb-entry, third-party-advisory
-
zerodayinitiative.com
/advisories/ZDI-17-521
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2017-11394
- NVD CVE-2017-11394
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.