CVE-2017-8217
First published: Tue Apr 25 2017(Updated: )
TP-Link C2 and C20i devices through firmware 0.9.1 4.2 v0032.0 Build 160706 Rel.37961n have too permissive iptables rules, e.g., SNMP is not blocked on any interface.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Tp-link C2 Firmware | <=0.9.1_4.2_v0032.0_build_160706 | |
| TP-Link C2 | ||
| Tp-link C20i Firmware | <=0.9.1_4.2_v0032.0_build_160706 | |
| Tp-link C20i |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2017-8217?
The severity of CVE-2017-8217 is rated as medium, with a score of 5.3.
What devices are affected by CVE-2017-8217?
CVE-2017-8217 affects TP-Link C2 and C20i devices running firmware version 0.9.1 4.2 v0032.0 Build 160706.
How do I fix CVE-2017-8217?
To mitigate CVE-2017-8217, upgrade to a firmware version that has improved iptables rules to block SNMP.
What is the primary issue with CVE-2017-8217?
The primary issue with CVE-2017-8217 is that the affected devices have overly permissive iptables rules, allowing SNMP traffic on all interfaces.
What company is responsible for the devices affected by CVE-2017-8217?
The company responsible for the devices affected by CVE-2017-8217 is TP-Link.
- collector/nvd-index
- vendor/tp-link
- product/c2 firmware
- canonical/tp-link c2 firmware
- product/c2
- canonical/tp-link c2
- product/c20i firmware
- canonical/tp-link c20i firmware
- product/c20i
- canonical/tp-link c20i