Skip to content

Silverstripe CMS information disclosure

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

Package

composer silverstripe/cms (Composer)

Affected versions

<= 4.5.0

Patched versions

None
composer silverstripe/framework (Composer)
>= 4.0.0, < 4.4.7
>= 4.5.0, < 4.5.4
4.4.7
4.5.4

Description

In SilverStripe through 4.5.0, a specific URL path configured by default through the silverstripe/framework module can be used to disclose the fact that a domain is hosting a Silverstripe application. There is no disclosure of the specific version. The functionality on this URL path is limited to execution in a CLI context, and is not known to present a vulnerability through web-based access. As a side-effect, this preconfigured path also blocks the creation of other resources on this path (e.g. a page).

References

Published by the National Vulnerability Database Jul 15, 2020
Published to the GitHub Advisory Database May 24, 2022
Reviewed Jul 13, 2023
Last updated May 22, 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.211%
(60th percentile)

Weaknesses

CVE ID

CVE-2020-6164

GHSA ID

GHSA-gm5x-hpmw-xpxg

Source code

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