| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in CX-One and CX-Protocol. It has been rated as critical. Impacted is an unknown function. This manipulation as part of Project File causes type conversion. This vulnerability appears as CVE-2018-19027. The attack requires local access. There is no available exploit.
Details
A vulnerability has been found in CX-One and CX-Protocol (version unknown) and classified as critical. Affected by this vulnerability is an unknown function. The manipulation as part of a Project File leads to a type conversion vulnerability. The CWE definition for the vulnerability is CWE-704. The product does not correctly convert an object, resource, or structure from one type to a different type. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Three type confusion vulnerabilities exist in CX-One Versions 4.50 and prior and CX-Protocol Versions 2.0 and prior when processing project files. An attacker could use a specially crafted project file to exploit and execute code under the privileges of the application.
The bug was discovered 01/10/2019. The weakness was presented 01/30/2019 by mr_me (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2018-19027 since 11/06/2018. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
The vulnerability was handled as a non-public zero-day exploit for at least 20 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 106524†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.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: Type conversionCWE: CWE-704
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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
11/06/2018 🔍01/10/2019 🔍
01/10/2019 🔍
01/30/2019 🔍
01/30/2019 🔍
01/31/2019 🔍
05/06/2020 🔍
Sources
Advisory: securityfocus.com⛔Researcher: mr_me
Status: Not defined
CVE: CVE-2018-19027 (🔍)
GCVE (CVE): GCVE-0-2018-19027
GCVE (VulDB): GCVE-100-130333
SecurityFocus: 106524 - Omron CX-Protocol CVE-2018-19027 Multiple Arbitrary Code Execution Vulnerabilities
Entry
Created: 01/31/2019 13:03Updated: 05/06/2020 20:07
Changes: 01/31/2019 13:03 (56), 05/06/2020 20:07 (4)
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.