dbcve.org
Email Encryption GatewayApplication · Trendmicro

CVE-2016-4351

CRITICAL · 9.8 CVSS v3.1 Published 2016-05-05
Fix available
A fix is available. Upgrade to after 5.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
SQL injection vulnerability in the authentication functionality in Trend Micro Email Encryption Gateway (TMEEG) 5.5 before build 1107 allows remote attackers to execute arbitrary SQL commands via unspecified vectors.

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 confidence

SQL injection vulnerability in the authentication functionality of Trend Micro Email Encryption Gateway (TMEEG) 5.5 before build 1107 allows remote attackers to execute arbitrary SQL commands via unspecified vectors. The flaw exists in how user-supplied input is handled during the authentication process, enabling attackers to manipulate SQL queries.

MitigationApply the vendor patch (build 1107 or later) to remediate the SQL injection vulnerability. Prior to patching, consider restricting network access to the authentication interface and implementing web application firewall rules as a temporary control.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 installed TMEEG version
    Access the Trend Micro Email Encryption Gateway admin console or check the product's About/Version information page to determine the exact version number
    Affected if The version displayed is 5.5 or lower
  2. Check build number
    Locate the build number in the product's version details or release notes - this is typically shown as 'Build XXXX' in the admin interface or product documentation
    Affected if The build number is below 1107 (for example, Build 1005, Build 1098, etc.)
  3. Verify authentication module accessibility
    Determine if the web-based authentication interface is exposed to network access - check firewall rules, network configuration, or try to access the login page from an external location if permitted
    Affected if The authentication portal is reachable from untrusted networks
  4. Review authentication logs for anomalies
    Examine TMEEG authentication and security logs for suspicious SQL-like error messages, failed login attempts with unusual characters, or indicators of SQL injection testing
    Affected if Logs contain SQL syntax errors or unusual query patterns in authentication attempts

A user is affected if their Trend Micro Email Encryption Gateway is version 5.5 with a build number lower than 1107 and the authentication interface is network-accessible.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 5.5
Interim mitigation

Apply the vendor patch (build 1107 or later) to remediate the SQL injection vulnerability. Prior to patching, consider restricting network access to the authentication interface and implementing web application firewall rules as a temporary control.

Recommended fix High confidence

Trend Micro Email Encryption Gateway 5.5 Build 1107

  1. Identify the current installed version of Trend Micro Email Encryption Gateway
  2. Download the updated version (build 1107 or later) from Trend Micro's official support portal at esupport.trendmicro.com
  3. Create a complete backup of the current configuration and any encrypted data before proceeding
  4. Follow Trend Micro's official upgrade procedure to install build 1107 or later
  5. After upgrade, verify the installation was successful and the SQL injection vulnerability is remediated
Caveat Review Trend Micro release notes for any configuration or compatibility changes required when upgrading to build 1107

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Email Encryption Gateway Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-4351 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2016-4351 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