Email Encryption GatewayApplication · Trendmicro

CVE-2018-10352

HIGH · 8.8 CVSS v3.0 Published 2018-05-23
Fix available
A fix is available. Upgrade to after 5.5 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
A vulnerability in Trend Micro Email Encryption Gateway 5.5 could allow a remote attacker to execute arbitrary SQL statements on vulnerable installations due to a flaw in the formConfiguration 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 · moderate confidence

SQL injection vulnerability in the formConfiguration class of Trend Micro Email Encryption Gateway 5.5 allows authenticated remote attackers to execute arbitrary SQL statements. The flaw exists in how user-supplied input is handled within the form configuration functionality, enabling database compromise.

MitigationApply vendor-provided patch from Trend Micro for Email Encryption Gateway 5.5. Until patch is available, restrict administrative access to trusted users only and implement network segmentation to limit exposure.

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
Email Encryption GatewayApplication
Affected:<= 5.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Trend Micro Email Encryption Gateway is installed
    Check for the product by examining installed software on the server, looking for directories named 'Trend Micro Email Encryption Gateway' or 'TEMPG' in Program Files, or checking running services for 'Trend Micro Email Encryption Gateway' processes.
    Affected if The product is found on the system.
  2. Determine the installed version of the product
    Locate the version information in the installation directory, typically found in an 'about' or 'version' file within the main product directory, or check the Windows registry under HKLM\SOFTWARE\TrendMicro\EmailEncryptionGateway for the Version value.
    Affected if The installed version is 5.5 or any version lower than 5.5.
  3. Verify if the web administrative interface is accessible
    Access the web interface URL for the Email Encryption Gateway (commonly on ports 8443, 443, or 8080) using a browser to confirm the login page is reachable from network locations.
    Affected if The administrative web interface is exposed and reachable.
  4. Confirm authentication is possible to the web interface
    Attempt to log in to the administrative interface with valid credentials or verify that valid administrator accounts exist in the system.
    Affected if Any authenticated administrative user account exists and can log in to the web interface.
  5. Check if form configuration functionality is accessible
    Navigate to the form configuration section within the administrative web interface after authentication, typically found under settings, configuration, or form management menus.
    Affected if The form configuration feature is accessible to authenticated administrators.

A user is affected if Trend Micro Email Encryption Gateway version 5.5 or lower is installed and the web administrative interface with form configuration is accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 5.5
Interim mitigation

Apply vendor-provided patch from Trend Micro for Email Encryption Gateway 5.5. Until patch is available, restrict administrative access to trusted users only and implement network segmentation to limit exposure.

Fix this in Email Encryption Gateway Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-10352 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-10352 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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