Service interruption via poisoned ARP traffic
Published Aug 19, 2021 · Updated Aug 3, 2024
Buffer overflow in TP-Link Wireless N Router WR840N allows adjacent authenticated attackers to disrupt routing through ARP poisoning. Public records do not identify the affected firmware versions, memory-handling locus, or the ARP input that overruns the buffer. An attacker must reach the same LAN and satisfy the low-privilege gate; successful exploitation interrupts Internet access for the router and connected devices.
Summary
What happened
Buffer overflow in TP-Link Wireless N Router WR840N allows adjacent authenticated attackers to disrupt routing through ARP poisoning. Public records do not identify the affected firmware versions, memory-handling locus, or the ARP input that overruns the buffer. An attacker must reach the same LAN and satisfy the low-privilege gate; successful exploitation interrupts Internet access for the router and connected devices.
The record
- CVE
- CVE-2021-29280
- Published
- Aug 19, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-668, T1557.002
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- upgraded-ARP-Poisoningfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo