FishEye and Crucible Security Advisory 2011-11-22
This advisory discloses a number of security vulnerabilities that we have found and fixed in versions of FishEye/Crucible earlier than 2.5.7. You need to upgrade your existing FishEye and Crucible installations to fix these vulnerabilities. Enterprise Hosted customers should request an upgrade by raising a support request at http://support.atlassian.com in the "Enterprise Hosting Support" project. Neither JIRA Studio nor Atlassian OnDemand are vulnerable to any of the issues described in this advisory.
Atlassian is committed to improving product security. The vulnerabilities listed in this advisory have been discovered by Atlassian, unless noted otherwise. The reporter may also have requested that we do not credit them.
If you have questions or concerns regarding this advisory, please raise a support request at http://support.atlassian.com/.
In this advisory:
XSS Vulnerabilities
Severity
Atlassian rates the severity level of these vulnerabilities as high, according to the scale published in Severity Levels for Security Issues. The scale allows us to rank the severity as critical, high, medium or low. These vulnerabilities are not critical.
Risk Assessment
We have identified and fixed a number of stored cross-site scripting (XSS) vulnerabilities which affect FishEye/Crucible instances, including publicly available instances (that is, internet-facing servers). XSS vulnerabilities allow an attacker to embed their own JavaScript into a FishEye/Crucible page. You can read more about XSS attacks on Wikipedia, at The Web Application Security Consortium and other places on the web.
Vulnerabilities
The table below describes the FishEye/Crucible versions and the specific functionality affected by the XSS vulnerabilities.
FishEye/Crucible Feature | Affected FishEye/Crucible Versions | Fixed Version | Issue Tracking |
|---|---|---|---|
FishEye user profile - display name | 2.5.4 and earlier | 2.5.5 | |
FishEye user profile - snippets in a user's comment | 2.5.4 and earlier | 2.5.5 |
Risk Mitigation
We recommend that you upgrade your FishEye/Crucible installation to fix these vulnerabilities.
Alternatively, if you are not in a position to upgrade immediately and you judge it necessary, you can disable public signup to your instance as a temporary mitigation until you have applied the upgrade. For tighter access control, you can restrict access to trusted groups.
Fix
FishEye and Crucible 2.5.5 and later versions fix two these issues. View the issues linked above for information on fix versions. You can download the latest versions of FishEye and Crucible from the download centres (FishEye download centre, Crucible download centre).
There are no patches available to fix these vulnerabilities. You must upgrade your FishEye/Crucible installation.
Permission Verification Vulnerabilities
Severity
Atlassian rates the severity level of these vulnerabilities as medium, according to the scale published in Severity Levels for Security Issues. The scale allows us to rank the severity as critical, high, medium or low. These vulnerabilities are not critical.
Risk Assessment
We have identified and fixed two permission verification bugs which affect FishEye/Crucible instances, including publicly available instances (that is, internet-facing servers). These vulnerabilities allow users to view metadata for changesets and reviews, from repositories/projects that they do not have access to, via tooltips.
Vulnerability
The table below describes the FishEye/Crucible versions and the specific functionality affected by the vulnerabilities.
| FishEye/Crucible Feature | Affected FishEye/Crucible Versions | Fixed Version | Issue Tracking |
|---|---|---|---|
| FishEye changeset tooltips | FishEye 2.4.6 to 2.5.6 | FishEye 2.5.7 | FE-3811 |
| Crucible review tooltips | Crucible 2.4.6 to 2.5.6 | Crucible 2.5.7 | CRUC-5811 |
Risk Mitigation
We recommend that you upgrade your FishEye/Crucible installation to fix these vulnerabilities.
Alternatively, if you are not in a position to upgrade immediately and you judge it necessary, you can disable anonymous access to your instance. Logged-in users will still be able to view metadata that they do not have permission to view, but anonymous users will be prevented from accessing this information.
Fix
FishEye and Crucible 2.5.7 and later versions fix these two issues. View the issues linked above for information on earlier fix versions for each issue. For a full description of this release, see the FishEye 2.5 changelog and Crucible 2.5 Changelog.You can download the latest version of FishEye and Crucible from the download centres (FishEye download centre, Crucible download centre).
There are no patches available to fix these vulnerabilities. You must upgrade your FishEye/Crucible installation.