-
Bug
-
Resolution: Fixed
-
Highest
-
2.1, 2.2, 2.3.1, 2.4.1, 2.5.1, 2.6.1, 2.7.1, 2.8.1, 2.9.1, 2.10.1, 2.11.1, 2.12.0, 3.0.0
-
None
-
Severity 1 - Critical
-
Crowd and Crowd Data Center had the pdkinstall development plugin incorrectly enabled in release builds. Attackers who can send unauthenticated or authenticated requests to a Crowd or Crowd Data Center instance can exploit this vulnerability to install arbitrary plugins, which permits remote code execution on systems running a vulnerable version of Crowd or Crowd Data Center.
Affected versions:
- All versions of Crowd from version 2.1.0 before 3.0.5 (the fixed version for 3.0.x), from version 3.1.0 before 3.1.6 (the fixed version for 3.1.x), from version 3.2.0 before 3.2.8 (the fixed version for 3.2.x), from version 3.3.0 before 3.3.5 (the fixed version for 3.3.x), and from version 3.4.0 before 3.4.4 (the fixed version for 3.4.x) are affected by this vulnerability.
Fix:
- Crowd and Crowd Data Center version 3.4.4 is available for download from https://www.atlassian.com/software/crowd/download
- Crowd and Crowd Data Center versions 3.0.5, 3.1.6, 3.2.8, and 3.3.5 are available for download from https://www.atlassian.com/software/crowd/download-archive
Mitigation
Atlassian recommends that you upgrade to the latest version. However, this issue can be mitigated as per the following instructions:
- Stop Crowd
- Find and delete any pdkinstall-plugin jar files from the Crowd installation directory and the data directory
- Remove the pdkinstall-plugin jar file from <Crowd installation directory>/crowd-webapp/WEB-INF/classes/atlassian-bundled-plugins.zip
- Start Crowd
- Check that there are no pdkinstall-plugin jar files in the installation directory or the data directory.
For additional details, see the full advisory.
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[CWD-5388] Crowd - pdkinstall development plugin incorrectly enabled - CVE-2019-11580
Hi paul981668836 thank you for reporting this to us!
We value feedback like this as we are doing our best to make our products secure. Regarding this issue and according to our current knowledge this problem does not occur in Crowd 3.5 version. However to be on the safe side we would like to learn more about the steps you've taken to reproduce this on Crowd 3.5 in your environment.
Please share details at: mkempa@atlassian.com
Thank you!
Marcin Kempa
This critical issue is present in 3.5.0 however it is not listed above as affected.
If you go to download crowd the version offered is 3.5.0 which includes this critical security vulnerability.
@SecurityB, Atlassian please could you help provide a fix/update for 3.5.x
Can support confirm that this issue has been patched/mitigated in Crowd 3.5.x? Much appreciated.
This is an independent assessment and you should evaluate its applicability to your own IT environment.
CVSS v3 score: 10.0 => Critical severity
Exploitability Metrics
| Attack Vector | Network |
|---|---|
| Attack Complexity | Low |
| Privileges Required | None |
| User Interaction | None |
Scope Metric
| Scope | Changed |
|---|
Impact Metrics
| Confidentiality | High |
|---|---|
| Integrity | High |
| Availability | High |
https://asecurityteam.bitbucket.io/cvss_v3/#CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Hi Marcin,
Apologies for the delay replying.
Our 3.5.0 Installation of Crowd on an AWS Server still had this issue however this was down to the upgrade process. There was a cache present on the box from the previous version. Once we cleared the cache we have been ok.
So to confirm the problem is not in 3.5.0.
Many thanks for your speedy response on this issue, it is very much appreciated.
kind regards
Paul.