CVE REMEDIATION GUIDE
CISA KEV · Known exploitedCriticalFixed-version data available

CVE-2019-11580 remediation guide

Atlassian Crowd and Crowd Data Center

Atlassian 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. 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...

Open CVE record
ProductAtlassian Crowd and Crowd Data Center
Affected versions2.1.0, unspecified, 3.1.0, 3.2.0, 3.3.0, 3.4.0, >= 2.1.0 < 3.0.5, >= 3.1.0 < 3.1.6, >= 3.2.0 < 3.2.8, >= 3.3.0 < 3.3.5, >= 3.4.0 < 3.4.4
Fixed versions3.0.5, 3.1.6, 3.2.8, 3.3.5, 3.4.4
Priority basisImmediate · CVSS 9.8 · EPSS 95.4%
01

Identify the affected asset

Confirm whether Atlassian Crowd and Crowd Data Center is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: 2.1.0, unspecified, 3.1.0, 3.2.0, 3.3.0, 3.4.0, >= 2.1.0 < 3.0.5, >= 3.1.0 < 3.1.6, >= 3.2.0 < 3.2.8, >= 3.3.0 < 3.3.5, >= 3.4.0 < 3.4.4. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Apply updates per vendor instructions.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.