SilverStripe Versioned Files module Unpublished files are exposed publicly
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| symbiote/silverstripe-versionedfiles Packagist |
| No fix yet |
| silverstripe/framework Packagist |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| symbiote/silverstripe-versionedfiles Packagist |
| No fix yet |
| silverstripe/framework Packagist |
|
|
In the Versioned Files module through 2.0.3 for SilverStripe 3.x, unpublished versions of files are publicly exposed to anyone who can guess their URL. This guess could be highly informed by a basic understanding of the symbiote/silverstripe-versionedfiles source code. (Users who upgrade from SilverStripe 3.x to 4.x and had Versioned Files installed have no further need for this module, because the 4.x release has built-in versioning. However, nothing in the upgrade process automates the destruction of these insecure artefacts, nor alerts the user to the criticality of destruction.)
From the CVE record · mitre
The Versioned Files module through 2.0.3 for SilverStripe 3.x publicly exposes unpublished files to anyone who can guess their URLs. No authentication or user interaction is needed. Upgrading from SilverStripe 3.x to 4.x does not automatically remove the insecure artefacts left by the module.
Check installations using symbiote/silverstripe-versionedfiles through 2.0.3 or silverstripe/framework 4.0.0–4.3.4 or 4.4.0–4.4.3.