novel-plus up to 4.3.0-RC1 /system/dataPerm/list offset/limit/sort sql injection
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
7.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in novel-plus up to 4.3.0-RC1. Affected is an unknown function of the file /system/dataPerm/list. The manipulation of the argument offset/limit/sort leads to sql injection. This vulnerability is traded as CVE-2024-24018. There is no exploit available. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Details
A vulnerability, which was classified as critical, has been found in novel-plus up to 4.3.0-RC1. This issue affects an unknown functionality of the file /system/dataPerm/list. The manipulation of the argument offset/limit/sort
with an unknown input 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. The summary by CVE is:
A SQL injection vulnerability exists in Novel-Plus v4.3.0-RC1 and prior versions. An attacker can pass in crafted offset, limit, and sort parameters to perform SQL injection via /system/dataPerm/list
The weakness was presented 02/08/2024. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2024-24018 since 01/25/2024. 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.
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: 7.6VulDB Meta Temp Score: 7.5
VulDB Base Score: 5.5
VulDB Temp Score: 5.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: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Partially
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
01/25/2024 🔍02/08/2024 🔍
02/08/2024 🔍
03/02/2024 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2024-24018 (🔍)
GCVE (CVE): GCVE-0-2024-24018
GCVE (VulDB): GCVE-100-253163
Entry
Created: 02/08/2024 10:14 AMUpdated: 03/02/2024 08:08 AM
Changes: 02/08/2024 10:14 AM (38), 03/02/2024 08:08 AM (11)
Complete: 🔍
Cache ID: 18:6D8:40
No comments yet. Languages: en.
Please log in to comment.