# CVE-2018-6222: Command injection in Trend Micro Email Encryption Gateway

> Attackers can manipulate log file locations to execute arbitrary commands on Trend Micro Email Encryption Gateway systems.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cmrj-247h-f4v8

## What is CVE-2018-6222?

CVE-2018-6222 is a high-severity command injection vulnerability in Trend Micro Email Encryption Gateway, published on 15 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Arbitrary logs location in Trend Micro Email Encryption Gateway 5.5 could allow an attacker to change location of log files and be manipulated to execute arbitrary commands and attain command execution on a vulnerable system.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2018-6222?

It affects 1 product.


Products: Trendmicro Email Encryption Gateway.

## How do I fix CVE-2018-6222?

No fix has been published for CVE-2018-6222 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-6222 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-6222 exists.

Public exploit code:

- Trend Micro Email Encryption Gateway 5.5 (Build 1111.00) - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in Trend Micro Email Encryption Gateway

- [CVE-2018-6220](https://insights.sbomify.com/CVE-2018-6220/): File upload in Trend Micro Email Encryption Gateway (critical 9.8)
- [CVE-2018-6223](https://insights.sbomify.com/CVE-2018-6223/): Missing authorization in Trend Micro Email Encryption Gateway (critical 9.8)
- [CVE-2018-6228](https://insights.sbomify.com/CVE-2018-6228/): SQL injection in Trend Micro Email Encryption Gateway (critical 9.8)
- [CVE-2018-6229](https://insights.sbomify.com/CVE-2018-6229/): SQL injection in Trend Micro Email Encryption Gateway (critical 9.8)
- [CVE-2016-4351](https://insights.sbomify.com/CVE-2016-4351/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-6222 and fix it if it is affected.

What it is: CVE-2018-6222 is a high-severity command injection vulnerability in Trend Micro Email Encryption Gateway, published on 15 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-6222 exists.

Affected product: Trend Micro Email Encryption Gateway. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-6222/ (Markdown: https://insights.sbomify.com/CVE-2018-6222/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-6222
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-6222
- OSV: https://osv.dev/vulnerability/CVE-2018-6222

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-6222/
Summaries are generated and may contain mistakes; the official description above is the record.