HipChat Server Security Advisory 2017-03-09
CVE-2017-5638 - Remote code execution in HipChat Server
|Advisory Release Date||
2 PM PST (Pacific Standard Time, -8 hours)
|Affected HipChat Server versions||
|Fixed HipChat Server versions||
Summary of Vulnerability
This advisory discloses a critical severity security vulnerability in HipChat Server. All versions of HipChat Server before version 2.2.2 are vulnerable.
Apache Struts2 Remote Code Execution (CVE-2017-5638)
Atlassian rates the severity level of this vulnerability as critical, according to the scale published in our Atlassian severity levels. The scale allows us to rank a severity as critical, high, moderate, or low.
This is an independent assessment and you should evaluate its applicability to your own IT environment.
HipChat Server includes a version of Crowd that has a version of the Apache Struts 2 library that is vulnerable to CVE-2017-5638. Attackers who have network access to a HipChat Server instance running a vulnerable version of HipChat Server can use this vulnerability to execute Java code of their choice and to make http requests to local & internal services.
All versions of HipChat Server before version 2.2.2 are affected by this vulnerability.
We have taken the following steps to address these issues:
- Released a patch for customers.
- Released HipChat Server version 2.2.2 that contains a fix for the issue.
All versions of HipChat Server before version 2.2.2 are affected by this vulnerability. This issue can be tracked here: HCPUB-2801 - Apache Struts 2 Remote Code Execution (CVE-2017-5638) Closed
What You Need to Do
The vulnerability and fix versions are described in the Description section above. Atlassian recommends that you upgrade to the latest version.
Upgrade HipChat Server to version 2.2.2
Information on upgrading HipChat Server can be found at Upgrading HipChat Server.
How do I check which version of HipChat Sever I am running?
You can check which version of HipChat Server you are running by going to cat /etc/hipchat-release.or by using ssh to log in to your HipChat Server and run
For a full description of the latest version of HipChat Server, see the release notes.
Given that we have confirmed exploitation in the wild, we recommend customers look for signs of compromise even if they upgrade immediately. Detection of such attacks is very environment-specific but below are some indicators that customers may find useful in their investigations.
The same expression can be used across all log types, which is especially useful if you are using a SIEM or log aggregator to analyze the logs all at once:
If remote code was executed, you will see an OGNL expression being evaluated on the server. These commands will typically start with `#cmd=` or `#cmds=` such as:
Similar to Crowd, HipChat's embedded Crowd version logs it's logs in `atlassian-crowd.log`. The default path is `/var/log/hipchat/atlassian-crowd.log`.
If you have questions or concerns regarding this advisory, please raise a support request at https://support.atlassian.com/customer/servicedesk-portal.
|Severity Levels for security issues||Atlassian security advisories include a severity level and a CVE identifier. This severity level is based on our self-calculated CVSS score for each specific vulnerability. CVSS is an industry standard vulnerability metric. You can also learn more about CVSS at https://www.first.org/cvss/user-guide.|
|End-of-Life Policy||Our end of life policy varies for different products. Please refer to our EoL Policy for details.|
Was this helpful?
Thanks for your feedback!