CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Snow 2.0.0. Affected is an unknown function of the component system/role/list. The manipulation of the argument dataScope leads to sql injection. This vulnerability is traded as CVE-2024-25168. It is possible to launch the attack remotely. 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 was found in Snow 2.0.0. It has been rated as critical. This issue affects an unknown code of the component system/role/list. The manipulation of the argument dataScope
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:
SQL injection vulnerability in snow snow v.2.0.0 allows a remote attacker to execute arbitrary code via the dataScope parameter of the system/role/list interface.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2024-25168 since 02/07/2024. The exploitation is known to be easy. The attack may be initiated remotely. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/02/2024). 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: 6.3VulDB Meta Temp Score: 6.2
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.3
CNA 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: 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
02/07/2024 🔍03/22/2024 🔍
03/22/2024 🔍
08/02/2024 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2024-25168 (🔍)
GCVE (CVE): GCVE-0-2024-25168
GCVE (VulDB): GCVE-100-257723
Entry
Created: 03/22/2024 02:48 PMUpdated: 08/02/2024 06:10 PM
Changes: 03/22/2024 02:48 PM (52), 08/02/2024 06:10 PM (11)
Complete: 🔍
Cache ID: 18:42D:40
I don't find the cpe into NVD NIST dictionary and into your vuldb_cpe_dictionary. Could you please help me to identify the technology and the cpe too?
Best Regards,
TEAM CERT
Best Regards,
TEAM CERT
Might our Artificial Intelligence support you?
Check our Alexa App!