CrowdApplication · Atlassian
CVE-2020-36240
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 · uneditedThe ResourceDownloadRewriteRule class in Crowd before version 4.0.4, and from version 4.1.0 before 4.1.2 allowed unauthenticated remote attackers to read arbitrary files within WEB-INF and META-INF directories via an incorrect path access check.
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 confidenceThe ResourceDownloadRewriteRule class in Atlassian Crowd contains a path traversal vulnerability that allows unauthenticated remote attackers to read arbitrary files within WEB-INF and META-INF directories due to an incorrect path access check. This could expose sensitive configuration files, application code, or credentials.
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
< 4.0.4>= 4.1.0, < 4.1.2CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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.
-
Identify Atlassian Crowd installationCheck for Crowd installation directories (e.g., /opt/atlassian/crowd, /var/atlassian/crowd, or Windows: C:\Atlassian\Crowd). Also check if crowd-webapp/WEB-INF/web.xml or similar Crowd web application files exist in common application server directories.Affected if Atlassian Crowd is installed on the system
-
Determine installed Crowd versionCheck the version file in the Crowd home directory (usually VERSION.txt or version.txt in the installation root), or access the Crowd admin interface and navigate to > Logging and Profiling or /admin/systeminfo to view the version.Affected if The installed version cannot be determined or is visible
-
Compare version against affected rangesReview the identified version against these affected ranges: versions < 4.0.4 OR versions >= 4.1.0 and < 4.1.2. Versions 4.0.4, 4.1.2 and later are not affected.Affected if The installed version falls within < 4.0.4 or >= 4.1.0 but < 4.1.2
-
Verify web application accessibilityCheck if the Crowd web interface is accessible over the network (typically ports 8095 or 443/8443). The vulnerability is exploitable via HTTP requests without authentication, so external accessibility increases risk.Affected if The Crowd web application is network-accessible from untrusted networks
The environment is affected if Atlassian Crowd is installed with a version matching < 4.0.4 or >= 4.1.0 but < 4.1.2, and the web application is accessible (even internally).
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 data4.0.44.1.2
Upgrade Atlassian Crowd to version 4.0.4 or 4.1.2 or later to remediate this vulnerability.
Fix this in Crowd
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-36240 — 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-2020-36240 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