CVE-2018-6229 in the critical feed json
A SQL injection vulnerability in an Trend Micro Email Encryption Gateway 5.5 edit policy script could allow an attacker to execute SQL comm…
published 8y ago modified 4mo ago also EUVD-2018-17990
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 10.2%
- EPSS 10.2% chance of exploitation in 30 days, percentile 95%
- public exploits
- 1
- Exploit-DB
Summary
A SQL injection vulnerability in an Trend Micro Email Encryption Gateway 5.5 edit policy script could allow an attacker to execute SQL commands to upload and execute arbitrary code that may harm the target system.
Patch / fix
Is CVE-2018-6229 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
10.25% chance of exploitation in the next 30 days, higher than 95% 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 | 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 Email Encryption Gateway
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
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-6229
- NVD CVE-2018-6229
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.