CVE-2018-6224 json
A lack of cross-site request forgery (CSRF) protection vulnerability in Trend Micro Email Encryption Gateway 5.5 could allow an attacker to…
published 8y ago modified 4mo ago also EUVD-2018-17985
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 81%
- public exploits
- 1
- Exploit-DB
Summary
A lack of cross-site request forgery (CSRF) protection vulnerability in Trend Micro Email Encryption Gateway 5.5 could allow an attacker to submit authenticated requests to a user browsing an attacker-controlled domain.
Patch / fix
Is CVE-2018-6224 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 FencerTimeline
- First public exploit (EDB-44166)
- Published
Exploit prediction
2.11% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-44166 Trend Micro Email Encryption Gateway 5.5 (Build 1111.00) - Multiple Vulnerabilities webapps, 2018-02-22
- coresecurity.com https://www.coresecurity.com/advisories/trend-micro-email-encryption-gateway-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 Email Encryption Gateway
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
success.trendmicro.com
/solution/1119349
patch, vendor-advisory
-
exploit-db.com
/exploits/44166/
exploit, third-party-advisory, vdb-entry
-
coresecurity.com
/advisories/trend-micro-email-encryption-gateway-multiple-vulnerabilities
exploit, technical-description, third-party-advisory
Sources
- CVE List CVE-2018-6224
- NVD CVE-2018-6224
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.