Supermicro CMS 3.11 setup.php font_type privilege escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Supermicro CMS 3.11. Affected by this vulnerability is an unknown functionality of the file setup.php. Performing a manipulation of the argument font_type results in an unknown weakness. This vulnerability was named CVE-2021-25857. There is no available exploit.
Details
A vulnerability, which was classified as critical, was found in Supermicro CMS 3.11 (Content Management System). This affects some unknown functionality of the file setup.php. The manipulation of the argument font_type with an unknown input leads to a unknown weakness. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in pcmt superMicro-CMS version 3.11, allows authenticated attackers to execute arbitrary code via the font_type parameter to setup.php.
The weakness was presented 08/11/2023. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2021-25857 since 01/22/2021. Technical details are known, but no exploit is available.
By approaching the search of inurl:setup.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.2
NVD Vector: 🔍
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: 🔍
Exploiting
Class: Privilege escalationCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/22/2021 🔍08/11/2023 🔍
08/11/2023 🔍
09/08/2023 🔍
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2021-25857 (🔍)
GCVE (CVE): GCVE-0-2021-25857
GCVE (VulDB): GCVE-100-236973
Entry
Created: 08/11/2023 17:37Updated: 09/08/2023 09:39
Changes: 08/11/2023 17:37 (38), 09/08/2023 09:39 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.