tindy2013 subconverter 0.6.4 API Endpoint sub?target=%TARGET%&url=%URL%&config=%CONFIG% denial of service
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 0.89 |
Summary
A vulnerability was found in tindy2013 subconverter 0.6.4. It has been rated as problematic. This issue affects some unknown processing of the file /sub?target=%TARGET%&url=%URL%&config=%CONFIG% of the component API Endpoint. This manipulation causes denial of service. This vulnerability is handled as CVE-2020-35579. There is not any exploit available.
Details
A vulnerability has been found in tindy2013 subconverter 0.6.4 and classified as problematic. Affected by this vulnerability is an unknown function of the file /sub?target=%TARGET%&url=%URL%&config=%CONFIG% of the component API Endpoint. The manipulation with an unknown input leads to a denial of service vulnerability. The CWE definition for the vulnerability is CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. As an impact it is known to affect availability.
The weakness was released 12/20/2020. The advisory is shared at github.com. This vulnerability is known as CVE-2020-35579. Technical details are known, but no exploit is available.
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
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.5
VulDB Base Score: 3.5
VulDB Temp Score: 3.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: Denial of serviceCWE: CWE-404
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
12/20/2020 🔍12/20/2020 🔍
12/20/2020 🔍
Sources
Product: github.comAdvisory: github.com
Status: Not defined
CVE: CVE-2020-35579 (🔍)
GCVE (CVE): GCVE-0-2020-35579
GCVE (VulDB): GCVE-100-166621
Entry
Created: 12/20/2020 22:08Changes: 12/20/2020 22:08 (37)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.