SpringBlade up to 2.7.1 DAO/DTO /api/blade-log/api/list asc/desc sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as critical has been found in SpringBlade up to 2.7.1. This issue affects some unknown processing of the file /api/blade-log/api/list of the component DAO/DTO. Such manipulation of the argument asc/desc as part of Parameter leads to sql injection. This vulnerability is listed as CVE-2020-16165. The attack may be performed from remote. There is no available exploit. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Details
A vulnerability was found in SpringBlade up to 2.7.1. It has been rated as critical. Affected by this issue is an unknown part of the file /api/blade-log/api/list of the component DAO/DTO. The manipulation of the argument asc/desc 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:
The DAO/DTO implementation in SpringBlade through 2.7.1 allows SQL Injection in an ORDER BY clause. This is related to the /api/blade-log/api/list ascs and desc parameters.
The weakness was presented 07/30/2020. This vulnerability is handled as CVE-2020-16165 since 07/30/2020. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1505 by the MITRE ATT&CK project.
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 best quality of vulnerability data, you may have to visit 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: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/30/2020 🔍07/30/2020 🔍
07/31/2020 🔍
06/03/2025 🔍
Sources
Status: Not definedCVE: CVE-2020-16165 (🔍)
GCVE (CVE): GCVE-0-2020-16165
GCVE (VulDB): GCVE-100-159218
Entry
Created: 07/31/2020 06:36 AMUpdated: 06/03/2025 04:45 PM
Changes: 07/31/2020 06:36 AM (37), 07/31/2020 06:41 AM (17), 06/03/2025 04:45 PM (16)
Complete: 🔍
Cache ID: 244:E9F:40
No comments yet. Languages: en.
Please log in to comment.