Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-14134: Stack-based Buffer Overflow in Linksys RE6500

0
High
VulnerabilityCVE-2025-14134cvecve-2025-14134
Published: Sat Dec 06 2025 (12/06/2025, 11:02:06 UTC)
Source: CVE Database V5
Vendor/Project: Linksys
Product: RE6500

Description

A vulnerability was determined in Linksys RE6500, RE6250, RE6300, RE6350, RE7000 and RE9000 1.0.013.001/1.0.04.001/1.0.04.002/1.1.05.003/1.2.07.001. Affected by this issue is the function RE2000v2Repeater_get_wireless_clientlist_setClientsName of the file mod_form.so. Executing manipulation of the argument clientsname_0 can lead to stack-based buffer overflow. The attack can be launched remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

AI-Powered Analysis

AILast updated: 12/06/2025, 11:12:15 UTC

Technical Analysis

CVE-2025-14134 is a stack-based buffer overflow vulnerability identified in several Linksys range extender models (RE6500, RE6250, RE6300, RE6350, RE7000, and RE9000) running specific firmware versions (1.0.013.001, 1.0.04.001, 1.0.04.002, 1.1.05.003, 1.2.07.001). The vulnerability resides in the function RE2000v2Repeater_get_wireless_clientlist_setClientsName within the mod_form.so library. This function improperly processes the argument clientsname_0, allowing an attacker to craft a malicious input that causes a stack-based buffer overflow. This overflow can be exploited remotely over the network without requiring authentication or user interaction, enabling an attacker to execute arbitrary code with elevated privileges on the device. The vulnerability has a CVSS 4.0 base score of 8.7, indicating high severity, with attack vector network (AV:N), low attack complexity (AC:L), no privileges required (PR:L), no user interaction (UI:N), and high impact on confidentiality, integrity, and availability (VC:H, VI:H, VA:H). The vendor was contacted early but has not issued any patches or advisories, and a public exploit has been disclosed, increasing the risk of exploitation. The affected devices are commonly used as wireless range extenders in both consumer and enterprise environments, potentially exposing internal networks to compromise if exploited. The lack of vendor response and public exploit availability necessitates immediate defensive actions by users and administrators.

Potential Impact

For European organizations, this vulnerability poses a significant risk due to the widespread use of Linksys range extenders in both home office and enterprise environments. Exploitation could allow attackers to gain unauthorized access to internal networks, bypass security controls, and execute arbitrary code on network devices, potentially leading to data breaches, lateral movement within corporate networks, and disruption of network availability. The high severity and remote exploitability without authentication make it a critical threat for organizations relying on these devices for network extension. Additionally, the absence of vendor patches increases the window of exposure, making mitigation challenging. Sensitive sectors such as finance, healthcare, and government agencies in Europe could face heightened risks due to the potential for espionage, data theft, or service disruption. The vulnerability could also be leveraged to establish persistent footholds or launch further attacks against connected systems.

Mitigation Recommendations

1. Immediately identify and inventory all Linksys range extenders in use, focusing on the affected models and firmware versions. 2. Where possible, disconnect vulnerable devices from the network or isolate them in segmented network zones to limit exposure. 3. Monitor network traffic for unusual activity targeting these devices, including malformed packets or attempts to exploit the clientsname_0 parameter. 4. Apply strict firewall rules to restrict access to the management interfaces of these devices, allowing only trusted IP addresses. 5. Regularly check for vendor updates or security advisories and apply patches promptly once available. 6. Consider replacing vulnerable devices with alternatives from vendors with active security support if patches are not forthcoming. 7. Implement network intrusion detection/prevention systems (IDS/IPS) with signatures for this vulnerability once available. 8. Educate IT staff and users about the risks associated with these devices and the importance of timely updates and network hygiene. 9. Conduct penetration testing and vulnerability scanning focused on network infrastructure to detect exploitation attempts. 10. Maintain up-to-date backups and incident response plans to quickly recover from potential compromises.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2025-12-05T17:07:15.702Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69340f40092893b302a4ad60

Added to database: 12/6/2025, 11:10:56 AM

Last enriched: 12/6/2025, 11:12:15 AM

Last updated: 12/6/2025, 12:36:55 PM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats