CrowdApplication · Atlassian
CVE-2019-20902
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUpgrading 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAtlassian Crowd versions before 3.4.6 and 3.5.0 before 3.5.1 contain a vulnerability where XML Data Transfer/import can reactivate users that were previously disabled in an OpenLDAP directory, allowing previously disabled accounts to become active again without proper authorization.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
CrowdApplication
< 3.4.6>= 3.5.0, < 3.5.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Atlassian Crowd versionCheck the Crowd application version via the Crowd administration console (About link in the footer) or by inspecting thecrowd-web-app/WEB-INF/lib directory for the crowd-*.jar file and its version metadata.Affected if The installed version is less than 3.4.6, or is 3.5.0.
-
Identify configured user directoriesIn Crowd admin console, go to User Directories and review the configured directories. Note which directories use the OpenLDAP connector.Affected if An OpenLDAP directory is configured as a user directory source.
-
Check for XML Data Transfer usageReview Crowd logs for XML import operations (search for 'XML' and 'import' or 'transfer' in the atlassian-crowd.log file in the logs directory). Also verify if any XML import files exist in the Crowd data directory.Affected if XML Data Transfer/import has been performed on the Crowd instance.
-
Verify user status synchronization behaviorCompare the disabled user count in Crowd's internal directory versus the OpenLDAP source by querying both directories for disabled accounts.Affected if Users disabled in OpenLDAP appear as active in Crowd's internal directory after an XML import was performed.
You are affected if your Crowd version is below 3.4.6 or is exactly 3.5.0, you have an OpenLDAP directory configured, and XML Data Transfer/import has been used, potentially allowing previously disabled LDAP users to become reactivated.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data3.4.63.5.1
Upgrade Atlassian Crowd to version 3.4.6, 3.5.1, or later to remediate this vulnerability.
Fix this in Crowd
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-20902 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-20902 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data