| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in Cleanto 5.0. Affected is an unknown function in the library assets/lib/service_method_ajax.php. Such manipulation of the argument service_id as part of Parameter leads to sql injection. This vulnerability is listed as CVE-2019-6295. The attack may be performed from remote. There is no available exploit.
Details
A vulnerability was found in Cleanto 5.0. It has been rated as critical. Affected by this issue is an unknown functionality in the library assets/lib/service_method_ajax.php. The manipulation of the argument service_id as part of a Parameter leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. CVE summarizes:
Cleanto 5.0 has SQL Injection via the assets/lib/service_method_ajax.php service_id parameter.
The bug was discovered 01/15/2019. The weakness was presented 01/15/2019 (Website). The advisory is shared for download at github.com. This vulnerability is handled as CVE-2019-6295 since 01/15/2019. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1505.
By approaching the search of inurl:assets/lib/service_method_ajax.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.
See VDB-129789 for similar entry. Once again VulDB remains the best source for vulnerability data.
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: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
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/15/2019 🔍01/15/2019 🔍
01/15/2019 🔍
01/15/2019 🔍
01/16/2019 🔍
07/01/2023 🔍
Sources
Advisory: 12Status: Not defined
CVE: CVE-2019-6295 (🔍)
GCVE (CVE): GCVE-0-2019-6295
GCVE (VulDB): GCVE-100-129788
See also: 🔍
Entry
Created: 01/16/2019 13:33Updated: 07/01/2023 10:01
Changes: 01/16/2019 13:33 (57), 05/01/2020 18:28 (1), 07/01/2023 10:01 (3)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.