First published: Tue Apr 20 2010(Updated: )
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.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Atlassian JIRA | =3.13.2 | |
Atlassian JIRA | =4.0.2 | |
Atlassian JIRA | =3.12 | |
Atlassian JIRA | =4.0.1 | |
Atlassian JIRA | =4.1 | |
Atlassian JIRA | =3.13.3 | |
Atlassian JIRA | =3.12.3 | |
Atlassian JIRA | =3.13.5 | |
Atlassian JIRA | =3.13.1 | |
Atlassian JIRA | =3.12.2 | |
Atlassian JIRA | =3.12.1 | |
Atlassian JIRA | =3.13.4 | |
Atlassian JIRA | =3.13 | |
Atlassian JIRA | =4.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.