Linksys RE6250/RE6300/RE6350/RE6500/RE7000/RE9000 portTriggerManageRule 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 vulnerability 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. This affects the function portTriggerManageRule of the file /goform/portTriggerManageRule. The manipulation of the argument triggerRuleName/schedule leads to stack-based buffer overflow. Remote exploitation of the attack is possible. The exploit has been disclosed to the public 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 portTriggerManageRule function on affected Linksys RE devices has a stack-based buffer overflow when handling the triggerRuleName or schedule argument. An attacker can exploit it remotely; the input does not specify whether authentication or user interaction is required. A public exploit has been disclosed.
Operators of Linksys RE6250, RE6300, RE6350, RE6500, RE7000, or RE9000 devices should check for the listed affected versions: 1.0.013.001, 1.0.04.001, 1.0.04.002, 1.1.05.003, and 1.2.07.001.