Milesight IP Security Camera up to 2016-11-14 SSL Private Key /etc/config hard-coded credentials
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Milesight IP Security Camera up to 2016-11-14. It has been declared as critical. Affected by this issue is some unknown functionality of the file /etc/config of the component SSL Private Key. Executing a manipulation can lead to hard-coded credentials. This vulnerability appears as CVE-2016-2357. The attack may be performed from remote. There is no available exploit.
Details
A vulnerability was found in Milesight IP Security Camera up to 2016-11-14. It has been declared as critical. This vulnerability affects some unknown processing of the file /etc/config of the component SSL Private Key. The manipulation with an unknown input leads to a hard-coded credentials vulnerability. The CWE definition for the vulnerability is CWE-798. The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
Milesight IP security cameras through 2016-11-14 have a hardcoded SSL private key under the /etc/config directory.
The weakness was presented 10/25/2019. This vulnerability was named CVE-2016-2357 since 02/12/2016. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1110.001 by the MITRE ATT&CK project.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-144181, VDB-144180, VDB-144179 and VDB-144177 for similar entries. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.5
VulDB Base Score: 7.3
VulDB Temp Score: 7.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: Hard-coded credentialsCWE: CWE-798 / CWE-259 / CWE-255
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
02/12/2016 🔍10/25/2019 🔍
10/26/2019 🔍
01/27/2024 🔍
Sources
Advisory: kirils.orgStatus: Not defined
CVE: CVE-2016-2357 (🔍)
GCVE (CVE): GCVE-0-2016-2357
GCVE (VulDB): GCVE-100-144178
See also: 🔍
Entry
Created: 10/26/2019 11:55Updated: 01/27/2024 13:51
Changes: 10/26/2019 11:55 (38), 10/26/2019 12:00 (17), 01/27/2024 13:51 (3)
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.