CVE-2018-10356
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA SQL injection remote code execution vulnerability in Trend Micro Email Encryption Gateway 5.5 could allow an attacker to execute arbitrary SQL statements on vulnerable installations due to a flaw in the formRequestDomains class. Authentication is required to exploit this vulnerability.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA SQL injection vulnerability in the formRequestDomains class of Trend Micro Email Encryption Gateway 5.5 allows authenticated attackers to inject arbitrary SQL statements. Successful exploitation can lead to remote code execution on the underlying database and potentially the host system.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 5.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Trend Micro Email Encryption Gateway is installedSearch the system for Trend Micro Email Encryption Gateway software, typically found in Program Files or similar directories. Look for installation directories containing 'Trend Micro' and 'Email Encryption Gateway' in the name.Affected if The software is present on the system
-
Check the installed versionLocate the version information for the installed Email Encryption Gateway. Common locations include the installation directory, registry keys, or the web interface login page. Compare your version to the affected range: version 5.5 and below.Affected if The installed version is 5.5 or lower
-
Verify the web management interface is accessibleCheck if the web-based administration console is accessible. The formRequestDomains class is part of this web interface. Attempt to access the management portal via HTTP/HTTPS on the configured port (commonly 8443 or 443).Affected if The web management interface is reachable and responds to requests
-
Confirm administrative authentication is configuredCheck if administrative accounts exist for the Email Encryption Gateway. The vulnerability requires an authenticated attacker, so verify whether local admin accounts or integrated authentication is enabled.Affected if Administrative accounts are configured and authentication is enabled for the web interface
-
Inspect formRequestDomains functionalityIf the web interface is accessible, navigate to the domain request functionality that corresponds to the formRequestDomains class. This is typically found in the email domain management or encryption settings section of the admin console.Affected if The domain management features controlled by formRequestDomains are accessible to authenticated users
The environment is affected if Trend Micro Email Encryption Gateway version 5.5 or lower is installed with its web management interface accessible and administrative authentication enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor patches immediately. If no patch is available, restrict administrative access to the affected interface and implement input validation/parameterized queries in the formRequestDomains class.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10356 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-10356 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data