CVE-2018-6219 json
An Insecure Update via HTTP vulnerability in Trend Micro Email Encryption Gateway 5.5 could allow an attacker to eavesdrop and tamper with…
published 8y ago modified 4mo ago also EUVD-2018-17980
- cvss
- 6.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.9%
- EPSS 3.9% chance of exploitation in 30 days, percentile 90%
- public exploits
- 1
- Exploit-DB
Summary
An Insecure Update via HTTP vulnerability in Trend Micro Email Encryption Gateway 5.5 could allow an attacker to eavesdrop and tamper with certain types of update data.
Is CVE-2018-6219 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
3.88% chance of exploitation in the next 30 days, higher than 90% 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 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:P/I:P/A:N |
Affected products
- Trend Micro Trend Micro Email Encryption Gateway
Classification
- Weakness
-
- CWE-295 Improper Certificate Validation
References
-
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
-
success.trendmicro.com
/solution/1119349
vendor-advisory
Sources
- CVE List CVE-2018-6219
- NVD CVE-2018-6219
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.