A vulnerability and two weaknesses have been reported in Atlassian JIRA Enterprise Edition, which can be exploited by malicious users to bypass certain security restrictions and malicious people to conduct cross-site scripting attacks and bypass certain security restrictions.

1) Certain input (e.g. passed via the URL to secure/CreateIssue) to 500page.jsp is not properly sanitised before being returned to the user in an error message. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site.

2) A weakness is caused due to an error when deleting shared filters. This can be exploited to delete the filters of another user.

3) A weakness is caused due to the setup wizard not correctly restricting access to the default language setting. This can be exploited to change the default language by manually accessing the setup wizard.

The vulnerability is confirmed in version 3.11 (build 288) and reported in JIRA Enterprise 3.6.4, 3.6.5, 3.10, and 3.12. The weaknesses are reported in versions prior to 3.12.1. Other versions may also be affected.

Solution
Update to version 3.12.1 or apply patches. See the vendor's advisory for details.
Further details available to Secunia VIM customers

Provided and/or discovered by
1) Adam 'Pooh' Ryba
2, 3) Reported by the vendor.

Changelog
Further details available to Secunia VIM customers

Original Advisory
http://confluence.atlassian.com/display/JIRA/JIRA+Security+Advisory+2007-12-24

Deep Links
Links available to Secunia VIM customers