Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 check_port_conflict stack-based overflow
Linksys RE6250 · Linksys RE6300 · Linksys RE6350 · Linksys RE6500
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linksys RE6250 |
| No fix yet |
| Linksys RE6300 |
|
Linksys RE6250 · Linksys RE6300 · Linksys RE6350 · Linksys RE6500
| Product | Affected | Fixed in |
|---|---|---|
| Linksys RE6250 |
| No fix yet |
| Linksys RE6300 |
|
1.1.05.0031.2.07.001| No fix yet |
| Linksys RE6350 |
| No fix yet |
| Linksys RE6500 |
| No fix yet |
| Linksys RE7000 |
| No fix yet |
| Linksys RE9000 |
| No fix yet |
A flaw has been found in Linksys RE6250, RE6300, RE6350, RE6500, RE7000 and RE9000 1.0.013.001/1.0.04.001/1.0.04.002/1.1.05.003/1.2.07.001. Impacted is the function check_port_conflict of the file /goform/check_port_conflict. Executing manipulation of the argument single_port_rule/port_range_rule can lead to stack-based buffer overflow. The attack can be executed remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
From the CVE record · VulDB
The check_port_conflict function in /goform/check_port_conflict is vulnerable to a stack-based buffer overflow when the single_port_rule or port_range_rule argument is manipulated. An attacker can trigger the flaw remotely; the input does not specify whether authentication or user interaction is required. An exploit has been published.
Operators of Linksys RE6250, RE6300, RE6350, RE6500, RE7000, or RE9000 devices running the listed versions—1.0.013.001, 1.0.04.001, 1.0.04.002, 1.1.05.003, or 1.2.07.001—should check their devices.