Vobot Clock up to 0.99.29 X.509 Certificate Crafted Certificate certificate validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Vobot Clock up to 0.99.29. This impacts an unknown function of the component X.509 Certificate. Executing a manipulation as part of Crafted Certificate can lead to certificate validation. This vulnerability is tracked as CVE-2018-6827. The attack can be launched remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability classified as critical was found in Vobot Clock up to 0.99.29. This vulnerability affects some unknown functionality of the component X.509 Certificate. The manipulation as part of a Crafted Certificate leads to a certificate validation vulnerability. The CWE definition for the vulnerability is CWE-295. The product does not validate, or incorrectly validates, a certificate. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
VOBOT CLOCK before 0.99.30 devices do not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information, and consequently execute arbitrary code, via a crafted certificate, as demonstrated by leveraging a hardcoded --no-check-certificate Wget option.
The bug was discovered 02/06/2018. The weakness was disclosed 02/09/2018 (Website). The advisory is available at stacksmashing.net. This vulnerability was named CVE-2018-6827 since 02/07/2018. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. The technical details are unknown and an exploit is not available. This vulnerability is assigned to T1587.003 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 3 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 0.99.30 eliminates this vulnerability.
The entries VDB-113121 and VDB-113120 are pretty similar. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
- 0.99.0
- 0.99.1
- 0.99.2
- 0.99.3
- 0.99.4
- 0.99.5
- 0.99.6
- 0.99.7
- 0.99.8
- 0.99.9
- 0.99.10
- 0.99.11
- 0.99.12
- 0.99.13
- 0.99.14
- 0.99.15
- 0.99.16
- 0.99.17
- 0.99.18
- 0.99.19
- 0.99.20
- 0.99.21
- 0.99.22
- 0.99.23
- 0.99.24
- 0.99.25
- 0.99.26
- 0.99.27
- 0.99.28
- 0.99.29
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.7
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.1
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: Certificate validationCWE: CWE-295 / CWE-287
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: Clock 0.99.30
Timeline
02/06/2018 🔍02/07/2018 🔍
02/09/2018 🔍
02/09/2018 🔍
02/10/2018 🔍
01/03/2020 🔍
Sources
Advisory: stacksmashing.netStatus: Not defined
CVE: CVE-2018-6827 (🔍)
GCVE (CVE): GCVE-0-2018-6827
GCVE (VulDB): GCVE-100-113122
See also: 🔍
Entry
Created: 02/10/2018 11:03Updated: 01/03/2020 19:55
Changes: 02/10/2018 11:03 (61), 01/03/2020 19:55 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.