6.5
CVSSv2

CVE-2015-5603

Published: 21/09/2015 Updated: 09/10/2018
CVSS v2 Base Score: 6.5 | Impact Score: 6.4 | Exploitability Score: 8
VMScore: 700
Vector: AV:N/AC:L/Au:S/C:P/I:P/A:P

Vulnerability Summary

The HipChat for JIRA plugin prior to 6.30.0 for Atlassian JIRA allows remote authenticated users to execute arbitrary Java code via unspecified vectors, related to "Velocity Template Injection Vulnerability."

Exploits

############################################################################ # JIRA and HipChat for JIRA plugin Velocity Template Injection Vulnerability # Date: 2015-08-26 # CVE ID: CVE-2015-5603 # Vendor Link: confluenceatlassiancom/jira/jira-and-hipchat-for-jira-plugin-security-advisory-2015-08-26-776650785html # # Product: JIRA and t ...
## # This module requires Metasploit: metasploitcom/download # Current source: githubcom/rapid7/metasploit-framework ## require 'msf/core' require 'json' class Metasploit3 < Msf::Exploit::Remote Rank = ExcellentRanking include Msf::Exploit::Remote::HttpClient include Msf::Exploit::EXE include Msf::Exploit::FileDropper ...

Metasploit Modules

Atlassian HipChat for Jira Plugin Velocity Template Injection

Atlassian Hipchat is a web service for internal instant messaging. A plugin is available for Jira that allows team collaboration at real time. A message can be used to inject Java code into a Velocity template, and gain code execution as Jira. Authentication is required to exploit this vulnerability, and you must make sure the account you're using isn't protected by captcha. By default, Java payload will be used because it is cross-platform, but you can also specify which native payload you want (Linux or Windows). HipChat for Jira plugin versions between 1.3.2 and 6.30.0 are affected. Jira versions between 6.3.5 and 6.4.10 are also affected by default, because they were bundled with a vulnerable copy of HipChat. When using the check command, if you supply a valid username and password, the module will be able to trigger the bug and check more accurately. If not, it falls back to passive, which can only tell if the target is running on a Jira version that is bundled with a vulnerable copy of Hipchat by default, which is less reliable. This vulnerability was originally discovered internally by Atlassian.

msf > use exploit/multi/http/jira_hipchat_template
      msf exploit(jira_hipchat_template) > show targets
            ...targets...
      msf exploit(jira_hipchat_template) > set TARGET <target-id>
      msf exploit(jira_hipchat_template) > show options
            ...show and set options...
      msf exploit(jira_hipchat_template) > exploit