JIRA and HipChat for JIRA Plugin - Velocity Template Injection

JIRA and HipChat for JIRA Plugin - Velocity Template Injection JIRA and HipChat for JIRA plugin Velocity Template Injection Vulnerability Date: 2015-08-26 CVE ID: CVE-2015-5603 Vendor Link:...

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...

JIRA and HipChat for JIRA Plugin - Velocity Template Injection

JIRA and HipChat for JIRA plugin Velocity Template Injection Vulnerability Date: 2015-08-26 CVE ID: CVE-2015-5603 Vendor Link: https://confluence.atlassian.com/jira/jira-and-hipchat-for-jira-plugin-security-advisory-2015-08-26-776650785.html Product: JIRA and the HipChat for JIRA plugin. Affected...

CVE-2015-6576: Bamboo - Deserialisation resulting in remote code execution

Note: the current version of this advisory can be found at https://confluence.atlassian.com/x/Hw7RLg . CVE ID: CVE-2015-6576 Product: Bamboo. Affected Bamboo product versions: 2.2 = version 5.8.5 5.9.0 = version 5.9.7 Summary: This advisory discloses a critical severity security vulnerability tha...

Active Directory/LDAP credentials stored in database in cleartext

We use an Active Directory server for authenticating our JIRA users, and a MySQL server for storing our JIRA data. We were extremely alarmed to discover that the username and password used for accessing the AD server are stored in cleartext in the MySQL database. Anyone who is able to compromise...

Active Directory/LDAP credentials stored in database in cleartext

We use an Active Directory server for authenticating our JIRA users, and a MySQL server for storing our JIRA data. We were extremely alarmed to discover that the username and password used for accessing the AD server are stored in cleartext in the MySQL database. Anyone who is able to compromise...

Active Directory/LDAP credentials stored in database in cleartext

We use an Active Directory server for authenticating our JIRA users, and a MySQL server for storing our JIRA data. We were extremely alarmed to discover that the username and password used for accessing the AD server are stored in cleartext in the MySQL database. Anyone who is able to compromise...

Prevent Activity feed information leakage by allowing permanently disabling of it

It seems that the sensitive information leakage is something almost impossible to avoid when you have a pair of JIRA instances, internal and external, which are connected one to another. Having them connected is clearly a business requirement for being able to cross link issues and to copy them...

Atlassian JIRA HipChat for JIRA Plugin Code Injection Vulnerability

Atlassian JIRA is a defect tracking management system from Atlassian Australia. HipChat for JIRA is a real-time collaborative plug-in for tracking and managing all types of issues and defects in the workplace. Atlassian JIRA HipChat for JIRA plugin version 6.30.0 before a security vulnerability...

CVE-2015-5603

The CVE-2015-5603 issue affects Atlassian Jira when used with the HipChat for Jira plugin (versions prior to 6.30.0). An authenticated Jira user can trigger a Velocity Template Injection in the plugin, enabling arbitrary Java code execution. Exploitation targets the plugin’s template handling and...

CVE-2015-5603: Improper Control of Generation of Code

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

Use integrated Windows Auth for Proxy Authentication

Hi, I'm looking to secure access to the internet via an authenticated proxy and would like to avoid username passwords within init strings. https://confluence.atlassian.com/display/JIRAKB/How+to+Configure+an+Outbound+HTTP+and+HTTPS+Proxy+for+JIRA describes a scenario where this may be possible,...

Atlassian JIRA < 5.0.7 Privilege Escalation

According to its self-reported version number, the version of Atlassian JIRA hosted on the remote web server is prior to 5.0.7. It is, therefore, potentially affected by a privilege escalation vulnerability. A remote attacker, using a crafted URL, can exploit this to bypass administrator-only...

Atlassian JIRA < 4.2.2 Open Redirect

According to its self-reported version number, the version of Atlassian JIRA hosted on the remote web server is prior to version 4.2.2. It is, therefore, potentially affected by an open redirect vulnerability due to improper sanitization of user-supplied input to an unspecified parameter. A remot...

Atlassian JIRA < 5.1.5 SOAP API Arbitrary File Overwrite

According to its self-reported version number, the version of Atlassian JIRA hosted on the remote web server is prior to version 5.1.5. It is, therefore, potentially affected by an arbitrary file overwrite vulnerability in the SOAP API used by JIRA. A remote, unauthenticated attacker can exploit...

Atlassian JIRA 4.2.x < 5.1.1 Multiple XSS

According to its self-reported version number, the version of Atlassian JIRA hosted on the remote web server is 4.2.x prior to 5.1.1. It is, therefore, potentially affected by multiple cross-site scripting XSS vulnerabilities that allow a remote attacker to embed arbitrary JavaScript code in a JI...

Atlassian JIRA 4.2.x < 5.1 XSRF

According to its self-reported version number, the version of Atlassian JIRA hosted on the remote web server is 4.2.x prior to 5.1. It is, therefore, potentially affected by a cross-site request forgery vulnerability, which could allow a remote attacker to trick a victim into posting issue commen...

Atlassian JIRA 4.3.x < 5.1.1 Multiple Open Redirect Vulnerabilities

According to its self-reported version number, the version of Atlassian JIRA hosted on the remote web server is 4.3.x prior to 5.1.1. It is, therefore, potentially affected by multiple open redirect vulnerabilities. A remote attacker, using a crafted URL, can exploit these vulnerabilities to...

Atlassian JIRA 4.2.x < 4.4 / 4.3.x < 4.4 Multiple XSS

According to its self-reported version number, the version of Atlassian JIRA hosted on the remote web server is 4.2.x or 4.3.x prior to version 4.4. It is, therefore, potentially affected by multiple cross-site scripting vulnerabilities, which can allow attackers to gain access to cookie-based...

Content Spoofing in AppPortalPage

A third party scan found that the ConvertIssue.jspa action is vulnerable to content spoofing, in specific text injection. In this case the content spoofing may be used to perform a phishing attack on users. How to reproduce:...