Our takeProgress restored ShareFile Storage Zones access after a four-day suspension over a credible external threat and shipped patches for versions before 5.12.4 and 6.0.1. Update if you self-host the controller (some enterprises); most smaller teams use hosted ShareFile and can ignore this.Cyber Resilience desk
Sources (4)
- infosec_mag · infosec_mag
- cccs · cccs
- cisa_advisories · cisa_advisories
- cccs · cccs
What this means for you — Security leader:If you self-host ShareFile Storage Zones Controller, confirm you are on v5.12.4+ or v6.0.1+ and that Storage Zones access is fully restored after the four-day suspension. Review logs covering the outage window for unusual activity.
What this means for you — Lean IT orgs:Only act if you run ShareFile Storage Zones Controller yourself—most lean-IT teams use hosted ShareFile and can ignore this. If unsure, ask your IT provider whether any on-prem controller is in your stack.
What this means for you — MSP:Inventory clients on ShareFile Storage Zones Controller v5/v6, push 5.12.4 or 6.0.1, and verify zones are back online after the suspension. Flag anyone still below those builds.
What this means for you — Researcher:Progress halted Storage Zones for four days over a credible external threat and shipped fixes for SZC v5 (<5.12.4) and v6 (<6.0.1)—compare advisory publish time to the outage window and any public exploit signal.