CVE-2019-20902: Upgrading Crowd via XML Data Transfer can reactivate a disabled user from OpenLDAP

This month

HIGH 7.5REMOTEUPGRADE

CVE-2019-20902 is a high-severity flaw (CVSS 7.5) affecting crowd. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Upgrading Crowd via XML Data Transfer can reactivate a disabled user from OpenLDAP. The affected versions are from before version 3.4.6 and from 3.5.0 before 3.5.1.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.9% (top 41%)
CISA exploited list	No
Published	2020-10-01
Last modified	2026-06-17

Publisher (CNA): Atlassian · Vendor: atlassian

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-10-01 02:15 UTCPublished CVE record published
2026-06-17 02:31 UTCUpdated Record last modified

atlassian crowd UPGRADE

Affected: < 3.4.6 · >= 3.5.0 and < 3.5.1

Fixed in: 3.4.6, 3.5.1

Safe to downgrade to: a release before 3.5.0

1. Check installed version

apt-cache policy crowd || rpm -q crowd || crowd --version

2. UPGRADE to 3.4.6 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade crowd

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade crowd

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 3.5.0 (Debian / Ubuntu)

apt-cache madison crowd sudo apt install crowd=<VERSION_BEFORE_3.5.0> sudo apt-mark hold crowd

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list crowd sudo dnf downgrade crowd-<VERSION_BEFORE_3.5.0> sudo dnf versionlock add crowd

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2019-20902?

crowd: upgrade to 3.4.6, 3.5.1. Exact commands for each OS are on this page.

Is CVE-2019-20902 being exploited?

CVE-2019-20902 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2019-20902 affect?

CVE-2019-20902 affects crowd. Severity is high (CVSS 7.5). Upgrading Crowd via XML Data Transfer can reactivate a disabled user from OpenLDAP. The affected versions are from before version 3.4.6 and from 3.5.0 before 3.5.1.

How urgent is CVE-2019-20902?

Priority 46/100. High severity; Remotely exploitable, no login, no user action

Software pages

OpenLDAP vulnerabilities

Related CVEs

CVE-2026-21589 HIGH 7.5 EXPLOITED UPGRADE UPGRADE Atlassian Multiple Products Files or Directories Accessible to External Parties Vulnerability
CVE-2026-21569 HIGH 7.9 UPGRADE This High severity XXE (XML External Entity Injection) vulnerability was introduced in version 7.1.0 of Crowd
CVE-2023-22521 HIGH 8.8 UPGRADE This High severity RCE (Remote Code Execution) vulnerability was introduced in version 3.4.6 of Crowd Data Cen
CVE-2022-43782 CRITICAL 9.8 UPGRADE Affected versions of Atlassian Crowd allow an attacker to authenticate as the crowd application via security m
CVE-2022-26137 HIGH 8.8 UPGRADE UPGRADE A vulnerability in multiple Atlassian products allows a remote, unauthenticated attacker to cause additional S

References

← Back to latest CVEs