3S-Smart CODESYS Control V3 up to 3.5.13.x Access Management Credentials access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in 3S-Smart CODESYS Control V3 up to 3.5.13.x. This vulnerability affects unknown code of the component Access Management. This manipulation causes access control (Credentials). The identification of this vulnerability is CVE-2018-10612. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability was found in 3S-Smart CODESYS Control V3 up to 3.5.13.x. It has been declared as problematic. Affected by this vulnerability is an unknown code of the component Access Management. The manipulation with an unknown input leads to a access control vulnerability (Credentials). The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect confidentiality. The summary by CVE is:
In 3S-Smart Software Solutions GmbH CODESYS Control V3 products prior to version 3.5.14.0, user access management and communication encryption is not enabled by default, which could allow an attacker access to the device and sensitive information, including user credentials.
The bug was discovered 12/18/2018. The weakness was shared 01/29/2019 (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2018-10612 since 05/01/2018. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 42 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 3.5.14.0 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 106248†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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
Name: CredentialsClass: Access control / Credentials
CWE: CWE-284 / CWE-266
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: CODESYS Control V3 3.5.14.0
Timeline
05/01/2018 🔍12/18/2018 🔍
12/18/2018 🔍
01/29/2019 🔍
01/29/2019 🔍
01/30/2019 🔍
07/29/2020 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
CVE: CVE-2018-10612 (🔍)
GCVE (CVE): GCVE-0-2018-10612
GCVE (VulDB): GCVE-100-130309
SecurityFocus: 106248 - 3S-Smart Software Solutions GmbH CODESYS ICSA-18-352-03 Access Bypass Vulnerability
Entry
Created: 01/30/2019 07:52Updated: 07/29/2020 15:17
Changes: 01/30/2019 07:52 (61), 07/29/2020 15:17 (3)
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.