Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
CriticalCISA KEVExploited in the wildPublic exploit

RCE in Atlassian Crowd pdkinstall Plugin

IdentifiersCVE-2019-11580CWE-306

Atlassian Crowd and Crowd Data Center shipped release builds with the pdkinstall development plugin incorrectly enabled. A remote attacker able to send HTTP requests to a vulnerable Crowd or Crowd Data Center instance can abuse this exposed plugin-installation functionality to install an arbitrary plugin. Because installed plugins execute within the application environment, successful exploitation results in remote code execution on the underlying Crowd server. According to the provided content, both unauthenticated and authenticated requests may be sufficient. Affected versions are Crowd 2.1.0 before 3.0.5, 3.1.0 before 3.1.6, 3.2.0 before 3.2.8, 3.3.0 before 3.3.5, and 3.4.0 before 3.4.4.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to install arbitrary plugins and thereby achieve remote code execution on the vulnerable Atlassian Crowd or Crowd Data Center host. This can provide full application-level compromise and likely server takeover, enabling follow-on actions such as web shell deployment, credential access, persistence, lateral movement, and use of the system as an initial foothold.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict network access to Crowd/Crowd Data Center so untrusted users cannot send requests to the application, especially from the internet. Limit exposure through segmentation, reverse-proxy or WAF controls, and administrative access restrictions. Monitor for suspicious plugin installation activity and investigate for indicators of compromise, including unexpected plugin artifacts or payloads such as attacker-supplied JAR files.

Remediation

Patch, then assume compromise.

Upgrade Atlassian Crowd or Crowd Data Center to a fixed release: 3.0.5 for the 3.0.x branch, 3.1.6 for 3.1.x, 3.2.8 for 3.2.x, 3.3.5 for 3.3.x, or 3.4.4 for 3.4.x, as applicable. More generally, remove the vulnerable release builds from service and deploy a vendor-fixed version in which the pdkinstall development plugin is not incorrectly enabled.
PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 1 / 1 TOTALView more in app
CVE-2019-11580MaturityPoCVerified exploit

This repository provides a working exploit for CVE-2019-11580, a remote code execution vulnerability in Atlassian Crowd and Crowd Data Center. The main exploit script (CVE-2019-11580.py) is written in Python and automates the process of uploading a malicious Java plugin (rce.jar) to the vulnerable /crowd/admin/uploadplugin.action endpoint. The plugin contains a servlet (exp.java) that acts as a webshell, allowing arbitrary command execution via HTTP requests to /crowd/plugins/servlet/exp with a 'cmd' parameter. The repository includes the Java source code for the webshell, a plugin descriptor (atlassian-plugin.xml), and a shell script (compile.sh) to build the malicious plugin. The README provides detailed usage instructions, affected versions (Crowd 2.1.0 through 3.4.4), and example commands. The exploit is operational and provides a remote shell on vulnerable targets.

jas502nDisclosed Jul 17, 2019pythonjavanetwork
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AtlassianCrowdapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures2

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity3

Community discussion across Reddit, Mastodon, and other social sources.