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.

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.

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.

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.

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.

Vulnerability/
CVE-2016-2357

critical

9.8

CWE

798

25/10/2019

5/8/2024

CVE-2016-2357

First published: Fri Oct 25 2019(Updated: )

Milesight IP security cameras through 2016-11-14 have a hardcoded SSL private key under the /etc/config directory.

Credit: cret@cert.org

Affected Software	Affected Version	How to fix
Milesight IP security camera firmware	<=2016-11-14
Milesight NCR Camera

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

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.
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.
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.
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.
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.

agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/author
agent/references
agent/weakness
agent/severity
agent/first-publish-date
agent/description
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/milesight
canonical/milesight ip security camera firmware
version/milesight ip security camera firmware/2016-11-14
canonical/milesight ncr camera

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

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.
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.
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.
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.
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.