First published: Mon Nov 27 2017(Updated: )
The locale feature in cgi-bin/luci on TP-Link TL-WVR, TL-WAR, TL-ER, and TL-R devices allows remote authenticated users to test for the existence of arbitrary files by making an operation=write;locale=%0d request, and then making an operation=read request with a crafted Accept-Language HTTP header, related to the set_sysinfo and get_sysinfo functions in /usr/lib/lua/luci/controller/locale.lua in uhttpd.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Tp-link Wvr300 Firmware | ||
TP-Link WVR300 | ||
TP-Link WVR302 Firmware | ||
TP-Link WVR302 | ||
Tp-link Wvr450l Firmware | ||
Tp-link Wvr450 | ||
Tp-link Wvr450l Firmware | ||
TP-Link WVR450L | ||
TP-Link TL-WVR450G Firmware | ||
TP-Link TL-WVR450G Firmware | ||
TP-Link TL-WVR458L Firmware | ||
TP-Link TL-WVR458L Firmware | ||
TP-Link TL-WVR458L | ||
TP-Link TL-WVR458L Firmware | ||
Tp-link Tl-wvr458p Firmware | ||
TP-Link TL-WVR458P | ||
TP-Link WVR900G Firmware | ||
TP-Link WVR900G | ||
TP-Link WVR900L Firmware | ||
TP-Link WVR900L Firmware | ||
TP-Link TL-WVR1200L | ||
TP-Link TL-WVR1200L Firmware | ||
Tp-link Wvr1300l Firmware | ||
TP-Link WVR1300L | ||
TP-Link TL-WVR1300G | ||
TP-Link TL-WAR1300G | ||
TP-Link TL-WVR1750L Firmware | ||
TP-Link WVR1750L | ||
Tp-link War2600l Firmware | ||
TP-Link WVR2600L | ||
TP-Link WVR4300L Firmware | ||
TP-Link WVR4300L Firmware | ||
TP-Link WAR302 | ||
TP-Link WAR302 | ||
TP-Link WR450L Firmware | ||
TP-Link WAR450 | ||
TP-Link WR450L Firmware | ||
TP-Link TL-WAR450L Firmware | ||
TP-Link TL-WAR458L Firmware | ||
TP-Link WAR458 | ||
TP-Link WAR458L Firmware | ||
TP-Link WAR458L | ||
TP-Link WDR900L Firmware | ||
TP-Link WAR900L | ||
TP-Link TL-WAR1200L Firmware | ||
TP-Link TL-WAR1200L Firmware | ||
TP-Link WAR1300L Firmware | ||
TP-Link WAR1300L | ||
TP-Link WAR1750L Firmware | ||
TP-Link WAR1750L Firmware | ||
TP-Link Archer WAR2600L | ||
TP-Link TL-ER3210G | ||
Tp-link Tl-er3210g Firmware | ||
TP-Link TL-ER3220G Firmware | ||
TP-Link TL-ER3220G Firmware | ||
TP-Link ER5110G Firmware | ||
TP-Link ER5110G Firmware | ||
TP-Link TL-ER5120G | ||
TP-Link TL-ER5120G Firmware | ||
TP-Link TL-ER5510G Firmware | ||
TP-Link TL-ER5510G Firmware | ||
TP-Link ER5520G Firmware | ||
TP-Link ER5520G | ||
TP-Link TL-ER6110G | ||
Tp-link Tl-er6110g Firmware | ||
Tp-link Tl-er6120g Firmware | ||
TP-Link TL-ER6120G | ||
TP-Link TL-ER6220G | ||
TP-Link TL-ER6220G | ||
TP-Link TL-ER6510G | ||
Tp-link Tl-er6510g Firmware | ||
TP-Link TL-ER6520G | ||
TP-Link TL-ER6520G Firmware | ||
Tp-link Tl-er7520g Firmware | ||
Tp-link Tl-er7520g Firmware | ||
Tp-link R473g Firmware | ||
TP-LINK R473 | ||
Tp-link R473g Firmware | ||
TP-LINK R473 | ||
TP-Link TL-R473P-AC | ||
TP-Link R473P-AC | ||
Tp-link Tl-r479gp-ac Firmware | ||
Tp-link Tl-r473gp-ac Firmware | ||
TP-Link TL-R478 Firmware | ||
TP-Link TL-R478 Firmware | ||
TP-Link TL-R478+ Firmware | ||
TP-Link TL-R478+ | ||
TP-Link TL-R478G Firmware | ||
TP-Link TL-R478G Firmware | ||
Tp-link Tl-r478g+ Firmware | ||
TP-Link TL-R478G+ | ||
TP-Link TL-R479P-AC | ||
Tp-link Tl-r479p-ac Firmware | ||
Tp-link Tl-r479gp-ac Firmware | ||
TP-Link TL-R479GPE-AC Firmware | ||
TP-Link TL-R479GPE-AC Firmware | ||
TP-Link TL-R483G | ||
TP-Link R483 Firmware | ||
Tp-link R483g Firmware | ||
TP-Link TL-R483G | ||
TP-Link TL-R488 | ||
TP-Link TL-R488 Firmware | ||
TP-Link TL-R4149G | ||
TP-Link R4149G | ||
TP-Link TL-R4239G Firmware | ||
TP-Link TL-R4239G Firmware | ||
Tp-link R4299g Firmware | ||
TP-Link TL-R4299G Firmware |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-16959 has a moderate severity rating as it allows unauthorized file access by authenticated users.
To mitigate CVE-2017-16959, update the firmware of the affected TP-Link devices to the latest version available.
CVE-2017-16959 affects specific models of TP-Link TL-WVR, TL-WAR, TL-ER, and TL-R series devices.
CVE-2017-16959 is a file disclosure vulnerability that can be exploited by remote authenticated users.
Currently, the best workaround for CVE-2017-16959 is to restrict access to the interface based on user roles until a firmware fix is applied.