Secunia

Thomas Pollet has discovered some vulnerabilities in Atlassian JIRA, which can be exploited by malicious people to conduct cross-site scripting and cross-site request forgery attacks, and by malicious users to conduct script insertion attacks.

1) Input passed via the "Full Name" parameter when altering a user profile is not properly sanitised before being stored. This can be exploited to insert arbitrary HTML and script code, which is executed in a user's browser session in context of an affected site when the malicious profile is viewed.

Successful exploitation requires a valid user account.

2) Input passed via the "returnUrl" parameter to "secure/AddComment!default.jspa" is not properly sanitised before being returned to the user. This can be exploited to execute arbitrary HTML and script code in a user's browser session in context of an affected site.

3) The application allows users to perform certain actions via HTTP requests without performing any validity checks to verify the request. This can be exploited to perform actions with the privileges of a target user, who is tricked into visiting a malicious website.

The vulnerabilities are confirmed in Atlassian JIRA Enterprise Edition version 3.13. Other versions may also be affected.

Solution
Update to version 3.13.1, which fixes vulnerabilities #1 and #2.
Further details available in Customer Area

Provided and/or discovered by
Thomas Pollet

Changelog
Further details available in Customer Area

Original Advisory
Atlassian:
http://confluence.atlassian.com/display/JIRA/JIRA+Security+Advisory+2008-10-29

Deep Links
Links available in Customer Area