CVE-2017-11398 json
A session hijacking via log disclosure vulnerability in Trend Micro Smart Protection Server (Standalone) versions 3.2 and below could allow…
published 2018-01-19 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-3025
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 8.2%
- EPSS 8.2% chance of exploitation in 30 days, percentile 94%
- public exploits
- 1
- Exploit-DB
Summary
A session hijacking via log disclosure vulnerability in Trend Micro Smart Protection Server (Standalone) versions 3.2 and below could allow an unauthenticated attacker to hijack active user sessions to perform authenticated requests on a vulnerable system.
Timeline
- First public exploit (EDB-43388)
- Published
Exploit prediction
8.20% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-08).
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 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected products
- Trend Micro Trend Micro Smart Protection Server (Standalone)
Classification
References
-
exploit-db.com
/exploits/43388/
exploit, third-party-advisory, vdb-entry
-
coresecurity.com
/advisories/trend-micro-smart-protection-server-multiple-vulnerabilities
exploit, third-party-advisory
-
success.trendmicro.com
/solution/1118992
vendor-advisory
-
securityfocus.com
/bid/102275
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-11398
- NVD CVE-2017-11398
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.