Edgecore ECS2020 1.0.0.0 HTTP Header /EXCU_SHELL command1 command injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Edgecore ECS2020 1.0.0.0. Affected by this issue is some unknown functionality of the file /EXCU_SHELL of the component HTTP Header Handler. This manipulation of the argument command1 causes command injection. This vulnerability is tracked as CVE-2019-6288. No exploit exists.
Details
A vulnerability has been found in Edgecore ECS2020 1.0.0.0 and classified as critical. Affected by this vulnerability is some unknown processing of the file /EXCU_SHELL of the component HTTP Header Handler. The manipulation of the argument command1 with an unknown input leads to a command injection vulnerability. The CWE definition for the vulnerability is CWE-77. The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability.
The weakness was disclosed 09/23/2021. The advisory is shared at twitter.com. This vulnerability is known as CVE-2019-6288 since 01/14/2019. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1202 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
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: Command injectionCWE: CWE-77 / CWE-74 / CWE-707
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
01/14/2019 🔍09/23/2021 🔍
09/23/2021 🔍
10/01/2021 🔍
Sources
Advisory: twitter.comStatus: Not defined
CVE: CVE-2019-6288 (🔍)
GCVE (CVE): GCVE-0-2019-6288
GCVE (VulDB): GCVE-100-183217
Entry
Created: 09/23/2021 05:33Updated: 10/01/2021 11:32
Changes: 09/23/2021 05:33 (39), 10/01/2021 11:32 (1)
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.