Shenzhim AAPTJS 1.3.1 Parameter list filePath privilege escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Shenzhim AAPTJS 1.3.1. This affects the function list of the component Parameter Handler. This manipulation of the argument filePath causes an unknown weakness.
This vulnerability appears as CVE-2020-36376. There is no available exploit.
Details
A vulnerability was found in Shenzhim AAPTJS 1.3.1. It has been declared as critical. Affected by this vulnerability is the function list of the component Parameter Handler. The manipulation of the argument filePath with an unknown input leads to a unknown weakness. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was presented 11/01/2021. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2020-36376 since 05/28/2021. Technical details of the vulnerability are known, but there is no available exploit.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
Website
- Product: https://github.com/shenzhim/aaptjs/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.5
VulDB Temp Score: 5.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Privilege escalationCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
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
05/28/2021 🔍11/01/2021 🔍
11/01/2021 🔍
11/04/2021 🔍
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2020-36376 (🔍)
GCVE (CVE): GCVE-0-2020-36376
GCVE (VulDB): GCVE-100-185803
Entry
Created: 11/01/2021 08:56Updated: 11/04/2021 09:47
Changes: 11/01/2021 08:56 (36), 11/01/2021 08:58 (1), 11/04/2021 09:47 (1)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.