Description
Atlassian JIRA 3.12 through 4.1 allows remote authenticated administrators to execute arbitrary code by modifying the (1) attachment (aka attachments), (2) index (aka indexing), or (3) backup path and then uploading a file, as exploited in the wild in April 2010.
Affected products
- Atlassian / Jira3.12 – 3.12
- Atlassian / Jira3.12.1 – 3.12.1
- Atlassian / Jira3.12.2 – 3.12.2
- Atlassian / Jira3.12.3 – 3.12.3
- Atlassian / Jira3.13 – 3.13
- Atlassian / Jira3.13.1 – 3.13.1
- Atlassian / Jira3.13.2 – 3.13.2
- Atlassian / Jira3.13.3 – 3.13.3
- Atlassian / Jira3.13.4 – 3.13.4
- Atlassian / Jira3.13.5 – 3.13.5
- Atlassian / Jira4.0 – 4.0
- Atlassian / Jira4.0.1 – 4.0.1
- Atlassian / Jira4.0.2 – 4.0.2
- Atlassian / Jira4.1 – 4.1
References
- MISChttps://exchange.xforce.ibmcloud.com/vulnerabilities/57828
- MISChttp://confluence.atlassian.com/display/JIRA/JIRA+Security+Advisory+2010-04-16
- MISChttp://jira.atlassian.com/browse/JRA-20995
- MAILING_LISThttp://www.openwall.com/lists/oss-security/2010/04/16/3
- MAILING_LISThttp://www.openwall.com/lists/oss-security/2010/04/16/4
- VENDOR_ADVISORYhttp://secunia.com/advisories/39353
- MISChttp://www.securityfocus.com/bid/39485
- MISChttp://jira.atlassian.com/browse/JRA-21004