CVE-2016-2357: Critical severity milesight ip security camera firmware vulnerability
Published Oct 25, 2019
·Updated
Milesight IP security cameras through 2016-11-14 have a hardcoded SSL private key under the /etc/config directory.
Affected Software
2 affected components
Milesight Ip Security Camera Firmware<=2016-11-14
Milesight IP security camera
Event History
Oct 25, 2019
CVE Published
via MITRE·12:46 PM
Data Sourced
via MITRE·12:46 PM
DescriptionWeakness
Frequently Asked Questions
1
What is the severity of CVE-2016-2357?
CVE-2016-2357 has a high severity rating due to the presence of a hardcoded SSL private key which can lead to unauthorized access.
2
How do I fix CVE-2016-2357?
To fix CVE-2016-2357, replace the hardcoded SSL private key with a secure, unique key and update the firmware if possible.
3
What devices are affected by CVE-2016-2357?
CVE-2016-2357 affects Milesight IP security camera firmware versions up to and including 2016-11-14.
4
What are the risks associated with CVE-2016-2357?
The risks associated with CVE-2016-2357 include potential interception of encrypted traffic and compromise of the camera system.
5
Is there a workaround for CVE-2016-2357?
A potential workaround for CVE-2016-2357 is to disable remote access to the cameras until the vulnerability is mitigated.