Sharefile Storagezones ControllerApplication · Citrix
CVE-2020-7473
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 · uneditedIn certain situations, all versions of Citrix ShareFile StorageZones (aka storage zones) Controller, including the most recent 5.10.x releases as of May 2020, allow unauthenticated attackers to access the documents and folders of ShareFile users. NOTE: unlike most CVEs, exploitability depends on the product version that was in use when a particular setup step was performed, NOT the product version that is in use during a current assessment of a CVE consumer's product inventory. Specifically, the vulnerability can be exploited if a storage zone was created by one of these product versions: 5.9.0, 5.8.0, 5.7.0, 5.6.0, 5.5.0, or earlier. This CVE differs from CVE-2020-8982 and CVE-2020-8983 but has essentially the same risk.
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 · moderate confidenceCitrix ShareFile StorageZones Controller allows unauthenticated attackers to access user documents and folders in certain configurations. The vulnerability is triggered specifically when storage zones were originally created using product versions 5.9.0 through 5.5.0 (or earlier), regardless of the current version deployed. This is a version-specific setup flaw rather than a current-code vulnerability.
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
Sharefile Storagezones ControllerApplication
<= 5.5.0= 5.6.0= 5.7.0= 5.8.0= 5.9.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 the StorageZones Controller version currently deployedCheck the installed version of Citrix ShareFile StorageZones Controller in the system inventory, control panel, or using the ShareFile administrative interface under the StorageZones Controller settings page.Affected if Current version is 5.9.0, 5.8.0, 5.7.0, 5.6.0, or 5.5.0 or earlier, or if the current version is unknown.
-
Determine the original creation version of each storage zoneReview storage zone metadata or migration history in the StorageZones Controller admin console to identify which version was used when the zone was initially created. Look for records of zone creation date and source version, or check upgrade/migration logs.Affected if Any storage zone was originally created using versions 5.5.0 through 5.9.0, regardless of the current version or patches applied.
-
Verify if storage zones were upgraded from vulnerable versionsCheck the upgrade or migration history for each storage zone in the administrative interface. Look for any indication that zones were initially provisioned with vulnerable versions and then upgraded in place.Affected if Storage zones were provisioned with versions 5.5.0-5.9.0 at any point, even if subsequently upgraded.
-
Review storage zone authentication configurationExamine the authentication settings for each storage zone in the StorageZones Controller configuration. Specifically check whether the zone is configured to accept unauthenticated requests or has default/weak authentication settings.Affected if Storage zones with origins in versions 5.5.0-5.9.0 retain the vulnerable authentication configuration.
The environment is affected if any storage zone was originally created using Citrix ShareFile StorageZones Controller versions 5.5.0 through 5.9.0, regardless of the current version deployed.
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 dataOrganizations must identify storage zones created with vulnerable versions (5.5.0-5.9.0) and recreate them using a patched version, or apply vendor-provided remediation to address the authentication bypass.
Fix this in Sharefile Storagezones Controller
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7473 — 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-7473 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