What is the severity of CVE-2016-8371?

CVE-2016-8371 is considered a critical vulnerability due to unauthorized access to the web server.

How do I fix CVE-2016-8371?

To fix CVE-2016-8371, ensure that the authentication mechanism is appropriately configured and enforced.

What systems are affected by CVE-2016-8371?

CVE-2016-8371 affects Phoenix Contact ILC PLCs with web server access vulnerabilities.

Is CVE-2016-8371 easily exploitable?

Yes, CVE-2016-8371 can be easily exploited as it allows unauthorized access even with authentication mechanisms enabled.

What are the consequences of CVE-2016-8371?

The consequences of CVE-2016-8371 include potential unauthorized control and manipulation of the PLC.

Vulnerability/
CVE-2016-8371

high

7.5

CWE

287 592

5/4/2018

16/9/2024

CVE-2016-8371

First published: Thu Apr 05 2018(Updated: )

The web server in Phoenix Contact ILC PLCs can be accessed without authenticating even if the authentication mechanism is enabled.

Credit: ics-cert@hq.dhs.gov

Affected Software	Affected Version	How to fix
Phoenixcontact Ilc Plcs Firmware
Phoenixcontact Ilc Plcs

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-8371?
CVE-2016-8371 is considered a critical vulnerability due to unauthorized access to the web server.
How do I fix CVE-2016-8371?
To fix CVE-2016-8371, ensure that the authentication mechanism is appropriately configured and enforced.
What systems are affected by CVE-2016-8371?
CVE-2016-8371 affects Phoenix Contact ILC PLCs with web server access vulnerabilities.
Is CVE-2016-8371 easily exploitable?
Yes, CVE-2016-8371 can be easily exploited as it allows unauthorized access even with authentication mechanisms enabled.
What are the consequences of CVE-2016-8371?
The consequences of CVE-2016-8371 include potential unauthorized control and manipulation of the PLC.

collector/nvd-index
agent/weakness
agent/type
agent/softwarecombine
agent/references
agent/severity
agent/author
agent/tags
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/event
agent/first-publish-date
agent/source
vendor/phoenixcontact
canonical/phoenixcontact ilc plcs firmware
canonical/phoenixcontact ilc plcs

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-8371?
CVE-2016-8371 is considered a critical vulnerability due to unauthorized access to the web server.
How do I fix CVE-2016-8371?
To fix CVE-2016-8371, ensure that the authentication mechanism is appropriately configured and enforced.
What systems are affected by CVE-2016-8371?
CVE-2016-8371 affects Phoenix Contact ILC PLCs with web server access vulnerabilities.
Is CVE-2016-8371 easily exploitable?
Yes, CVE-2016-8371 can be easily exploited as it allows unauthorized access even with authentication mechanisms enabled.
What are the consequences of CVE-2016-8371?
The consequences of CVE-2016-8371 include potential unauthorized control and manipulation of the PLC.