CrowdApplication · Atlassian
CVE-2017-18110
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 administration backup restore resource in Atlassian Crowd before version 3.0.2 and from version 3.1.0 before version 3.1.1 allows remote attackers to read files from the filesystem via a XXE vulnerability.
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 confidenceAn XML External Entity (XXE) vulnerability in the administration backup restore feature of Atlassian Crowd allows remote authenticated attackers to read arbitrary files from the server's filesystem by uploading a malicious XML backup file containing crafted entity references.
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.0.2= 3.1.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 if Atlassian Crowd is installedLocate the Crowd installation directory and check for crowd-webapp or Crowd application filesAffected if Crowd is not installed, this CVE does not apply
-
Determine the installed Crowd versionCheck the version file or About page within the Crowd administration interface, or examine the crowd-*-version.jar file in the installation directoryAffected if The version is less than 3.0.2 or exactly 3.1.0
-
Verify the backup restore feature is accessibleConfirm the Crowd administration console is accessible and the backup/restore functionality is enabled for the authenticated administratorAffected if The backup restore feature is available and the attacker can access it with admin credentials
-
Check if XML external entity processing is enabledReview the XML parser configuration used by the backup restore functionality - typically in the application server or Crowd XML handling librariesAffected if External entity processing is enabled in the XML parser, allowing crafted entity references to resolve and read arbitrary files
A user is affected if they are running Atlassian Crowd version 3.0.0, 3.0.1, or 3.1.0 with the administration backup restore feature accessible to authenticated attackers and XML external entity processing enabled in the parser.
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.0.2
Upgrade Atlassian Crowd to version 3.0.2, 3.1.1, or later. These versions include fixes that disable external entity processing in the XML parser used by the backup restore functionality.
Fix this in Crowd
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18110 — 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-2017-18110 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