What is the severity of CVE-2017-5891?

CVE-2017-5891 is classified as a medium severity vulnerability due to its potential for unauthorized access to router configuration.

How do I fix CVE-2017-5891?

To fix CVE-2017-5891, upgrade your ASUS RT-AC* and RT-N* devices firmware to version 3.0.0.4.380.7378 or later.

What types of attacks can CVE-2017-5891 facilitate?

CVE-2017-5891 allows attackers to exploit Cross-Site Request Forgery (CSRF) vulnerabilities to change router settings without user consent.

Which ASUS devices are affected by CVE-2017-5891?

CVE-2017-5891 affects ASUS RT-AC and RT-N series devices that are running firmware versions prior to 3.0.0.4.380.7378.

What can happen if I don’t address CVE-2017-5891?

If CVE-2017-5891 is not addressed, it may lead to unauthorized configuration changes or access to the network.

Vulnerability/
CVE-2017-5891

high

8.8

CWE

352

10/5/2017

16/5/2017

CVE-2017-5891: CSRF

First published: Wed May 10 2017(Updated: )

ASUS RT-AC* and RT-N* devices with firmware before 3.0.0.4.380.7378 have Login Page CSRF and Save Settings CSRF.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
ASUS RT-AC1750 B1 Firmware	=3.0.0.4.380.7266
ASUS RT-AC1750 firmware

Remedy

https://www.asus.com/support/Download/11/2/0/161/45/

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-5891?
CVE-2017-5891 is classified as a medium severity vulnerability due to its potential for unauthorized access to router configuration.
How do I fix CVE-2017-5891?
To fix CVE-2017-5891, upgrade your ASUS RT-AC* and RT-N* devices firmware to version 3.0.0.4.380.7378 or later.
What types of attacks can CVE-2017-5891 facilitate?
CVE-2017-5891 allows attackers to exploit Cross-Site Request Forgery (CSRF) vulnerabilities to change router settings without user consent.
Which ASUS devices are affected by CVE-2017-5891?
CVE-2017-5891 affects ASUS RT-AC and RT-N series devices that are running firmware versions prior to 3.0.0.4.380.7378.
What can happen if I don’t address CVE-2017-5891?
If CVE-2017-5891 is not addressed, it may lead to unauthorized configuration changes or access to the network.

agent/references
agent/type
agent/tags
agent/event
agent/last-modified-date
agent/first-publish-date
collector/nvd-index
agent/software-canonical-lookup-request
agent/description
agent/severity
agent/author
agent/weakness
agent/remedy
agent/softwarecombine
vendor/asus
canonical/asus rt-ac1750 b1 firmware
version/asus rt-ac1750 b1 firmware/3.0.0.4.380.7266
canonical/asus rt-ac1750 firmware

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-5891?
CVE-2017-5891 is classified as a medium severity vulnerability due to its potential for unauthorized access to router configuration.
How do I fix CVE-2017-5891?
To fix CVE-2017-5891, upgrade your ASUS RT-AC* and RT-N* devices firmware to version 3.0.0.4.380.7378 or later.
What types of attacks can CVE-2017-5891 facilitate?
CVE-2017-5891 allows attackers to exploit Cross-Site Request Forgery (CSRF) vulnerabilities to change router settings without user consent.
Which ASUS devices are affected by CVE-2017-5891?
CVE-2017-5891 affects ASUS RT-AC and RT-N series devices that are running firmware versions prior to 3.0.0.4.380.7378.
What can happen if I don’t address CVE-2017-5891?
If CVE-2017-5891 is not addressed, it may lead to unauthorized configuration changes or access to the network.