What is the severity of CVE-2017-16731?

CVE-2017-16731 is classified as a critical vulnerability due to its potential for credential exposure during authentication processes.

How do I fix CVE-2017-16731?

To remediate CVE-2017-16731, apply the latest patches or updates for ABB Ellipse software that address this vulnerability.

What impact could CVE-2017-16731 have on my system?

CVE-2017-16731 could allow attackers to intercept and exploit unprotected credentials sent during the LDAP authentication process.

Which versions of ABB Ellipse are affected by CVE-2017-16731?

CVE-2017-16731 affects ABB Ellipse versions from 8.3 to 8.9 released prior to December 2017.

Is there a workaround for CVE-2017-16731?

Currently, no official workaround for CVE-2017-16731 is provided, so updating to a fixed version is the recommended action.

Vulnerability/
CVE-2017-16731

high

8.8

CWE

522 523

20/12/2017

16/5/2023

CVE-2017-16731

First published: Wed Dec 20 2017(Updated: )

An Unprotected Transport of Credentials issue was discovered in ABB Ellipse 8.3 through Ellipse 8.9 released prior to December 2017 (including Ellipse Select). A vulnerability exists in the authentication of Ellipse to LDAP/AD using the LDAP protocol. An attacker could exploit the vulnerability by sniffing local network traffic, allowing the discovery of authentication credentials.

Credit: ics-cert@hq.dhs.gov

Affected Software	Affected Version	How to fix
Hitachienergy Ellipse	>=8.3.0<=8.9.0

Never miss a vulnerability like this again

Reference Links

https://ics-cert.us-cert.gov/advisories/ICSA-17-353-01

Frequently Asked Questions

What is the severity of CVE-2017-16731?
CVE-2017-16731 is classified as a critical vulnerability due to its potential for credential exposure during authentication processes.
How do I fix CVE-2017-16731?
To remediate CVE-2017-16731, apply the latest patches or updates for ABB Ellipse software that address this vulnerability.
What impact could CVE-2017-16731 have on my system?
CVE-2017-16731 could allow attackers to intercept and exploit unprotected credentials sent during the LDAP authentication process.
Which versions of ABB Ellipse are affected by CVE-2017-16731?
CVE-2017-16731 affects ABB Ellipse versions from 8.3 to 8.9 released prior to December 2017.
Is there a workaround for CVE-2017-16731?
Currently, no official workaround for CVE-2017-16731 is provided, so updating to a fixed version is the recommended action.

collector/nvd-index
agent/references
agent/weakness
agent/severity
agent/author
agent/tags
agent/type
agent/description
agent/event
agent/last-modified-date
agent/first-publish-date
agent/softwarecombine
vendor/hitachienergy
canonical/hitachienergy ellipse
version/hitachienergy ellipse/8.3.0
version/hitachienergy ellipse/8.9.0

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-2017-16731?
CVE-2017-16731 is classified as a critical vulnerability due to its potential for credential exposure during authentication processes.
How do I fix CVE-2017-16731?
To remediate CVE-2017-16731, apply the latest patches or updates for ABB Ellipse software that address this vulnerability.
What impact could CVE-2017-16731 have on my system?
CVE-2017-16731 could allow attackers to intercept and exploit unprotected credentials sent during the LDAP authentication process.
Which versions of ABB Ellipse are affected by CVE-2017-16731?
CVE-2017-16731 affects ABB Ellipse versions from 8.3 to 8.9 released prior to December 2017.
Is there a workaround for CVE-2017-16731?
Currently, no official workaround for CVE-2017-16731 is provided, so updating to a fixed version is the recommended action.