What is the severity of CVE-2018-17926?

CVE-2018-17926 has a high severity level due to the potential for unauthorized file uploads and subsequent remote code execution.

How do I fix CVE-2018-17926?

To fix CVE-2018-17926, upgrade the M2M ETHERNET firmware to version 2.23 or later and the ETH-FW firmware to version 1.02 or later.

What types of devices are affected by CVE-2018-17926?

CVE-2018-17926 affects the M2M ETHERNET products using firmware versions 2.22 and prior, as well as ETH-FW firmware versions 1.01 and prior.

What can an attacker do with CVE-2018-17926?

An attacker can exploit CVE-2018-17926 to bypass user authentication and upload malicious files, potentially leading to system compromise.

Is there a workaround for CVE-2018-17926?

Currently, there are no known workarounds for CVE-2018-17926 aside from applying the recommended firmware updates.

Vulnerability/
CVE-2018-17926

medium

4.3

CWE

287

18/12/2018

5/8/2024

CVE-2018-17926

First published: Tue Dec 18 2018(Updated: )

The product M2M ETHERNET (FW Versions 2.22 and prior, ETH-FW Versions 1.01 and prior) is vulnerable in that an attacker can upload a malicious language file by bypassing the user authentication mechanism.

Credit: ics-cert@hq.dhs.gov

Affected Software	Affected Version	How to fix
Abb Eth-fw Firmware	<=1.01
Abb Fw Firmware	<=2.22
Abb M2M Ethernet

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-17926?
CVE-2018-17926 has a high severity level due to the potential for unauthorized file uploads and subsequent remote code execution.
How do I fix CVE-2018-17926?
To fix CVE-2018-17926, upgrade the M2M ETHERNET firmware to version 2.23 or later and the ETH-FW firmware to version 1.02 or later.
What types of devices are affected by CVE-2018-17926?
CVE-2018-17926 affects the M2M ETHERNET products using firmware versions 2.22 and prior, as well as ETH-FW firmware versions 1.01 and prior.
What can an attacker do with CVE-2018-17926?
An attacker can exploit CVE-2018-17926 to bypass user authentication and upload malicious files, potentially leading to system compromise.
Is there a workaround for CVE-2018-17926?
Currently, there are no known workarounds for CVE-2018-17926 aside from applying the recommended firmware updates.

agent/references
agent/type
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/author
agent/weakness
agent/softwarecombine
agent/description
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/abb
canonical/abb eth-fw firmware
version/abb eth-fw firmware/1.01
canonical/abb fw firmware
version/abb fw firmware/2.22
canonical/abb m2m ethernet

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-2018-17926?
CVE-2018-17926 has a high severity level due to the potential for unauthorized file uploads and subsequent remote code execution.
How do I fix CVE-2018-17926?
To fix CVE-2018-17926, upgrade the M2M ETHERNET firmware to version 2.23 or later and the ETH-FW firmware to version 1.02 or later.
What types of devices are affected by CVE-2018-17926?
CVE-2018-17926 affects the M2M ETHERNET products using firmware versions 2.22 and prior, as well as ETH-FW firmware versions 1.01 and prior.
What can an attacker do with CVE-2018-17926?
An attacker can exploit CVE-2018-17926 to bypass user authentication and upload malicious files, potentially leading to system compromise.
Is there a workaround for CVE-2018-17926?
Currently, there are no known workarounds for CVE-2018-17926 aside from applying the recommended firmware updates.