CVE-2025-14134
BaseFortify
Publication date: 2025-12-06
Last updated on: 2025-12-10
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linksys | re6500_firmware | 1.0.013.001 |
| linksys | re6500 | * |
| linksys | re6250_firmware | 1.0.04.001 |
| linksys | re6250 | * |
| linksys | re6300_firmware | 1.2.07.001 |
| linksys | re6300 | * |
| linksys | re6350_firmware | 1.0.04.001 |
| linksys | re6350 | * |
| linksys | re7000_firmware | 1.1.05.003 |
| linksys | re7000 | * |
| linksys | re9000_firmware | 1.0.04.002 |
| linksys | re9000 | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-119 | The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data. |
| CWE-121 | A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a stack-based buffer overflow in certain Linksys repeater models (RE6500, RE6250, RE6300, RE6350, RE7000, and RE9000) in specific firmware versions. It occurs in the function RE2000v2Repeater_get_wireless_clientlist_setClientsName within the mod_form.so file. By manipulating the argument clientsname_0 remotely, an attacker can trigger this overflow, potentially leading to arbitrary code execution or system compromise.
How can this vulnerability impact me? :
This vulnerability can allow a remote attacker to execute arbitrary code or cause a denial of service on affected Linksys repeater devices. This could lead to unauthorized control over the device, disruption of network services, or further attacks on the network infrastructure.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection can involve monitoring network traffic for unusual or malformed packets targeting the wireless client list functionality of affected Linksys repeater models. Since the vulnerability is triggered by manipulation of the clientsname_0 argument in the RE2000v2Repeater_get_wireless_clientlist_setClientsName function, inspecting HTTP or other protocol requests to the device for suspiciously long or malformed clientsname_%d parameters may indicate exploitation attempts. Specific commands are not provided in the resources, but using network packet capture tools (e.g., tcpdump or Wireshark) to filter for traffic to the affected devices and analyzing for abnormal client name parameters could help detect attempts. Additionally, checking device logs for crashes or abnormal behavior related to the wireless client list function may assist in detection. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing affected devices, as no known countermeasures or vendor patches are available. Since the vulnerability allows remote exploitation and no vendor response has been provided, isolating the vulnerable devices from untrusted networks or disabling vulnerable functionality if possible may reduce risk. Monitoring for exploit attempts and applying network-level protections such as firewall rules to restrict access to the affected devices can also help mitigate exposure. [2]