QCubed up to 3.1.1 POST Request profile.php strProfileData deserialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in QCubed up to 3.1.1. It has been classified as critical. The affected element is an unknown function of the file profile.php of the component POST Request Handler. The manipulation of the argument strProfileData leads to deserialization. This vulnerability is listed as CVE-2020-24914. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in QCubed up to 3.1.1. It has been rated as critical. This issue affects an unknown code block of the file profile.php of the component POST Request Handler. The manipulation of the argument strProfileData with an unknown input leads to a deserialization vulnerability. Using CWE to declare the problem leads to CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. Impacted is confidentiality, integrity, and availability.
The weakness was presented 03/05/2021. The advisory is shared at ait.ac.at. The identification of this vulnerability is CVE-2020-24914. Technical details are known, but no exploit is available.
By approaching the search of inurl:profile.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
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: DeserializationCWE: CWE-502 / CWE-20
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
08/28/2020 🔍03/05/2021 🔍
03/05/2021 🔍
03/28/2021 🔍
Sources
Advisory: ait.ac.atStatus: Not defined
CVE: CVE-2020-24914 (🔍)
GCVE (CVE): GCVE-0-2020-24914
GCVE (VulDB): GCVE-100-170693
Entry
Created: 03/05/2021 07:04Updated: 03/28/2021 11:36
Changes: 03/05/2021 07:04 (37), 03/07/2021 08:45 (2), 03/28/2021 11:36 (18)
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.