MaEPSBroker up to 2.5.0.31 brokerCommand command injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.0 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in MaEPSBroker up to 2.5.0.31. Affected by this issue is some unknown functionality. This manipulation of the argument brokerCommand causes command injection. This vulnerability is tracked as CVE-2020-7839. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as critical was found in MaEPSBroker up to 2.5.0.31. Affected by this vulnerability is some unknown processing. The manipulation of the argument brokerCommand 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 03/25/2021. It is possible to read the advisory at krcert.or.kr. This vulnerability is known as CVE-2020-7839. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1202 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.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
- 2.5.0.0
- 2.5.0.1
- 2.5.0.2
- 2.5.0.3
- 2.5.0.4
- 2.5.0.5
- 2.5.0.6
- 2.5.0.7
- 2.5.0.8
- 2.5.0.9
- 2.5.0.10
- 2.5.0.11
- 2.5.0.12
- 2.5.0.13
- 2.5.0.14
- 2.5.0.15
- 2.5.0.16
- 2.5.0.17
- 2.5.0.18
- 2.5.0.19
- 2.5.0.20
- 2.5.0.21
- 2.5.0.22
- 2.5.0.23
- 2.5.0.24
- 2.5.0.25
- 2.5.0.26
- 2.5.0.27
- 2.5.0.28
- 2.5.0.29
- 2.5.0.30
- 2.5.0.31
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 8.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD 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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Command injectionCWE: CWE-77 / 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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
01/22/2020 🔍03/25/2021 🔍
03/25/2021 🔍
04/04/2021 🔍
Sources
Advisory: krcert.or.krStatus: Not defined
CVE: CVE-2020-7839 (🔍)
GCVE (CVE): GCVE-0-2020-7839
GCVE (VulDB): GCVE-100-171667
Entry
Created: 03/25/2021 07:16Updated: 04/04/2021 17:24
Changes: 03/25/2021 07:16 (35), 04/04/2021 17:19 (2), 04/04/2021 17:24 (19)
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.