Skip to content

SilverStripe Folders migrated from 3.x may be unsafe to upload to

High severity GitHub Reviewed Published May 24, 2022 to the GitHub Advisory Database • Updated Apr 25, 2024

Package

composer silverstripe/assets (Composer)

Affected versions

>= 1.0.0, < 1.4.7
>= 1.5.0, < 1.5.2

Patched versions

1.4.7
1.5.2
composer silverstripe/framework (Composer)
>= 4.0.0, < 4.4.6
4.4.6
composer silverstripe/userforms (Composer)
>= 5.0.0, < 5.4.2
5.4.2

Description

In SilverStripe through 4.5, files uploaded via Forms to folders migrated from Silverstripe CMS 3.x may be put to the default "/Uploads" folder instead. This affects installations which allowed upload folder protection via the optional silverstripe/secureassets module under 3.x. This module is installed and enabled by default on the Common Web Platform (CWP). The vulnerability only affects files uploaded after an upgrade to 4.x.

References

Published by the National Vulnerability Database Apr 15, 2020
Published to the GitHub Advisory Database May 24, 2022
Reviewed Apr 25, 2024
Last updated Apr 25, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.232%
(62nd percentile)

Weaknesses

CVE ID

CVE-2020-9280

GHSA ID

GHSA-592m-4533-rxq9

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.