| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in pouetnet pouet 2.0. The affected element is an unknown function. Performing a manipulation of the argument howmany results in sql injection. This vulnerability is identified as CVE-2020-36648. There is not any exploit available. It is suggested to install a patch to address this issue.
Details
A vulnerability, which was classified as critical, was found in pouetnet pouet 2.0. This affects an unknown code. The manipulation of the argument howmany with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was released 01/08/2023 as 11d615931352066fb2f6dcb07428277c2cd99baf. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2020-36648. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
Applying the patch 11d615931352066fb2f6dcb07428277c2cd99baf is able to eliminate this problem. The bugfix is ready for download at github.com. The advisory contains the following remark:
fix minor SQL injection
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
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
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 11d615931352066fb2f6dcb07428277c2cd99baf
Timeline
01/08/2023 🔍01/08/2023 🔍
01/08/2023 🔍
01/30/2023 🔍
Sources
Advisory: 11d615931352066fb2f6dcb07428277c2cd99bafStatus: Confirmed
CVE: CVE-2020-36648 (🔍)
GCVE (CVE): GCVE-0-2020-36648
GCVE (VulDB): GCVE-100-217641
Entry
Created: 01/08/2023 10:26Updated: 01/30/2023 08:34
Changes: 01/08/2023 10:26 (42), 01/30/2023 08:31 (2), 01/30/2023 08:34 (28)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.