| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in SilverStripe up to 2.4.3. This issue affects some unknown processing of the file sapphire/silverstripe_version. The manipulation leads to access control. This vulnerability is uniquely identified as CVE-2010-5078. No exploit exists. It is suggested to upgrade the affected component.
Details
A vulnerability was found in SilverStripe up to 2.4.3 (Content Management System). It has been rated as problematic. This issue affects an unknown code of the file sapphire/silverstripe_version. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-264. Impacted is confidentiality. The summary by CVE is:
SilverStripe 2.3.x before 2.3.10 and 2.4.x before 2.4.4 stores sensitive information under the web root with insufficient access control, which allows remote attackers to obtain version information via a direct request to (1) apphire/silverstripe_version or (2) cms/silverstripe_version.
The weakness was disclosed 12/10/2010 (Website). The advisory is shared at openwall.com. The identification of this vulnerability is CVE-2010-5078 since 12/19/2011. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
Upgrading to version 2.3.2 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at X-Force (63990), SecurityFocus (BID 45367†), OSVDB (69888†) and Secunia (SA42346†). The entries VDB-61857, VDB-61856, VDB-62298 and VDB-62296 are pretty similar. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: SilverStripe 2.3.2
Timeline
12/10/2010 🔍12/10/2010 🔍
12/13/2010 🔍
12/13/2010 🔍
12/13/2010 🔍
12/19/2011 🔍
09/17/2012 🔍
03/24/2015 🔍
12/13/2021 🔍
Sources
Advisory: 5031Status: Not defined
Confirmation: 🔍
CVE: CVE-2010-5078 (🔍)
GCVE (CVE): GCVE-0-2010-5078
GCVE (VulDB): GCVE-100-62297
X-Force: 63990
SecurityFocus: 45367 - SilverStripe Multiple Remote Vulnerabilities
Secunia: 42346 - SilverStripe Multiple Vulnerabilities, Moderately Critical
OSVDB: 69888 - SilverStripe sapphire/silverstripe_version Version Information Disclosure
See also: 🔍
Entry
Created: 03/24/2015 12:22Updated: 12/13/2021 21:36
Changes: 03/24/2015 12:22 (50), 09/14/2017 09:33 (13), 12/13/2021 21:36 (3)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.