What is the severity of CVE-2018-17012?

The severity of CVE-2018-17012 is medium (6.5).

How does CVE-2018-17012 affect TP-Link TL-WR886N devices?

Authenticated attackers can crash router services on TP-Link TL-WR886N devices via a long JSON data payload.

Which versions of TP-Link TL-WR886N are affected by CVE-2018-17012?

TP-Link TL-WR886N 6.0 2.3.4 and TL-WR886N 7.0 1.1.0 devices are affected.

How can authenticated attackers exploit CVE-2018-17012?

Authenticated attackers can crash router services such as inetd, HTTP, DNS, and UPnP by sending long JSON data for the hosts_info set_block_flag up_limit.

Is TP-Link TL-WR886N version 6.0_2.3.4 vulnerable to CVE-2018-17012?

Yes, TP-Link TL-WR886N version 6.0_2.3.4 is vulnerable to CVE-2018-17012.

Is TP-Link TL-WR886N version 7.0_1.1.0 vulnerable to CVE-2018-17012?

Yes, TP-Link TL-WR886N version 7.0_1.1.0 is vulnerable to CVE-2018-17012.

How can I fix the vulnerability in TP-Link TL-WR886N devices?

There is currently no known fix for this vulnerability. It is recommended to monitor for vendor updates or patches.

Where can I find more information about CVE-2018-17012?

More information about CVE-2018-17012 can be found at the following reference: https://github.com/PAGalaxyLab/VulInfo/blob/master/TP-Link/WR886N/inetd_task_dos_08/README.md

Vulnerability/
CVE-2018-17012

medium

6.5

13/9/2018

17/9/2024

CVE-2018-17012

First published: Thu Sep 13 2018(Updated: )

An issue was discovered on TP-Link TL-WR886N 6.0 2.3.4 and TL-WR886N 7.0 1.1.0 devices. Authenticated attackers can crash router services (e.g., inetd, HTTP, DNS, and UPnP) via long JSON data for hosts_info set_block_flag up_limit.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Tp-link Tl-wr886n Firmware	=6.0_2.3.4
Tp-link Tl-wr886n Firmware	=7.0_1.1.0
TP-Link TL-WR886N

Never miss a vulnerability like this again

Reference Links

https://github.com/PAGalaxyLab/VulInfo/blob/master/TP-Link/WR886N/inetd_task_dos_08/README.md

Frequently Asked Questions

What is the severity of CVE-2018-17012?
The severity of CVE-2018-17012 is medium (6.5).
How does CVE-2018-17012 affect TP-Link TL-WR886N devices?
Authenticated attackers can crash router services on TP-Link TL-WR886N devices via a long JSON data payload.
Which versions of TP-Link TL-WR886N are affected by CVE-2018-17012?
TP-Link TL-WR886N 6.0 2.3.4 and TL-WR886N 7.0 1.1.0 devices are affected.
How can authenticated attackers exploit CVE-2018-17012?
Authenticated attackers can crash router services such as inetd, HTTP, DNS, and UPnP by sending long JSON data for the hosts_info set_block_flag up_limit.
Is TP-Link TL-WR886N version 6.0_2.3.4 vulnerable to CVE-2018-17012?
Yes, TP-Link TL-WR886N version 6.0_2.3.4 is vulnerable to CVE-2018-17012.
Is TP-Link TL-WR886N version 7.0_1.1.0 vulnerable to CVE-2018-17012?
Yes, TP-Link TL-WR886N version 7.0_1.1.0 is vulnerable to CVE-2018-17012.
How can I fix the vulnerability in TP-Link TL-WR886N devices?
There is currently no known fix for this vulnerability. It is recommended to monitor for vendor updates or patches.
Where can I find more information about CVE-2018-17012?
More information about CVE-2018-17012 can be found at the following reference: https://github.com/PAGalaxyLab/VulInfo/blob/master/TP-Link/WR886N/inetd_task_dos_08/README.md

collector/nvd-index
agent/references
agent/severity
agent/author
agent/type
agent/event
agent/description
agent/last-modified-date
agent/softwarecombine
agent/first-publish-date
agent/tags
collector/mitre-cve
source/MITRE
vendor/tp-link
canonical/tp-link tl-wr886n firmware
version/tp-link tl-wr886n firmware/6.0_2.3.4
version/tp-link tl-wr886n firmware/7.0_1.1.0
canonical/tp-link tl-wr886n

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.