Geutebruck G-Code/G-Cam up to 1.12.0.25 os command injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.0 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Geutebruck G-Code and G-Cam up to 1.12.0.25. The impacted element is an unknown function. This manipulation causes os command injection. This vulnerability is handled as CVE-2019-10958. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in Geutebruck G-Code and G-Cam up to 1.12.0.25. It has been declared as critical. Affected by this vulnerability is an unknown functionality. The manipulation with an unknown input leads to a os command injection vulnerability. The CWE definition for the vulnerability is CWE-78. The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Geutebruck IP Cameras G-Code(EEC-2xxx), G-Cam(EBC-21xx/EFD-22xx/ETHC-22xx/EWPC-22xx): All versions 1.12.0.25 and prior may allow a remote authenticated attacker with access to network configuration to supply system commands to the server, leading to remote code execution as root.
The weakness was released 01/17/2020. This vulnerability is known as CVE-2019-10958 since 04/08/2019. The attack can be launched remotely. The successful exploitation needs a single authentication. Neither technical details nor an exploit are publicly 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.
Entries connected to this vulnerability are available at VDB-149100 and VDB-149099. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
- 1.12.0.0
- 1.12.0.1
- 1.12.0.2
- 1.12.0.3
- 1.12.0.4
- 1.12.0.5
- 1.12.0.6
- 1.12.0.7
- 1.12.0.8
- 1.12.0.9
- 1.12.0.10
- 1.12.0.11
- 1.12.0.12
- 1.12.0.13
- 1.12.0.14
- 1.12.0.15
- 1.12.0.16
- 1.12.0.17
- 1.12.0.18
- 1.12.0.19
- 1.12.0.20
- 1.12.0.21
- 1.12.0.22
- 1.12.0.23
- 1.12.0.24
- 1.12.0.25
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: 8.8
VulDB Temp Score: 8.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.2
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: Os command injectionCWE: CWE-78 / CWE-77 / CWE-74
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
04/08/2019 🔍01/17/2020 🔍
01/18/2020 🔍
03/24/2024 🔍
Sources
Advisory: us-cert.govStatus: Not defined
CVE: CVE-2019-10958 (🔍)
GCVE (CVE): GCVE-0-2019-10958
GCVE (VulDB): GCVE-100-149101
See also: 🔍
Entry
Created: 01/18/2020 08:44Updated: 03/24/2024 15:28
Changes: 01/18/2020 08:44 (35), 01/18/2020 08:49 (17), 03/24/2024 15:28 (17)
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.