liftkit database up to 2.13.1 src/Query/Query.php processOrderBy sql injection
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.9 | $0-$5k | 0.06 |
A vulnerability was found in liftkit database up to 2.13.1. It has been classified as critical. This affects the function processOrderBy
of the file src/Query/Query.php. The manipulation with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The software 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. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was released 01/15/2023 as 42ec8f2b22e0b0b98fb5b4444ed451c1b21d125a. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2016-15020. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.
By approaching the search of inurl:src/Query/Query.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 2.13.2 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 42ec8f2b22e0b0b98fb5b4444ed451c1b21d125a is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. The advisory contains the following remark:
Fixed orderBy injection vulnerability
Product
Vendor
Name
License
- open-source
CPE 2.3
CPE 2.2
CVSSv3
VulDB Meta Base Score: 6.9VulDB Meta Temp Score: 6.9
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔒
CNA Base Score: 5.5
CNA Vector (VulDB): 🔒
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
ATT&CK: T1505
Local: No
Remote: Partially
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: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: database 2.13.2
Patch: 42ec8f2b22e0b0b98fb5b4444ed451c1b21d125a
Timeline
01/15/2023 Advisory disclosed01/15/2023 CVE reserved
01/15/2023 VulDB entry created
02/07/2023 VulDB last update
Sources
Advisory: 42ec8f2b22e0b0b98fb5b4444ed451c1b21d125aStatus: Confirmed
CVE: CVE-2016-15020 (🔒)
Entry
Created: 01/15/2023 11:24 AMUpdated: 02/07/2023 05:52 PM
Changes: 01/15/2023 11:24 AM (45), 02/07/2023 05:45 PM (2), 02/07/2023 05:52 PM (28)
Complete: 🔍
No comments yet. Languages: en.
Please log in to comment.