CVE-2025-9361
BaseFortify
Publication date: 2025-08-23
Last updated on: 2025-09-02
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| 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 | re6500_firmware | 1.0.013.001 |
| linksys | re6500 | * |
| 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?
CVE-2025-9361 is a critical stack-based buffer overflow vulnerability in multiple Linksys range extender models. It occurs in the function ipRangeBlockManageRule within the file /goform/ipRangeBlockManageRule. By manipulating the input parameters ipRangeBlockRuleName, scheduleIp, or ipRangeBlockRuleIpAddr with crafted data exceeding expected lengths, an attacker can trigger a stack overflow. This flaw allows remote exploitation without authentication, potentially leading to arbitrary code execution or crashing the device. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing a remote attacker to execute arbitrary code on the affected device or cause it to crash, leading to loss of confidentiality, integrity, and availability. Since the exploit is publicly available and requires low attack complexity, it poses a significant security risk. There are currently no known mitigations or patches, so affected devices may need to be replaced to ensure security. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring or testing the affected Linksys range extenders (models RE6250, RE6300, RE6350, RE6500, RE7000, and RE9000) for attempts to access or manipulate the /goform/ipRangeBlockManageRule endpoint with unusually long or crafted parameters (ipRangeBlockRuleName, scheduleIp, ipRangeBlockRuleIpAddr) that could trigger a stack-based buffer overflow. Since the exploit is public, penetration testing tools or scripts from the public proof-of-concept exploit repositories (such as GitHub) can be used to simulate the attack. Network monitoring tools can be configured to alert on HTTP POST requests to /goform/ipRangeBlockManageRule with suspicious payload sizes or patterns. Specific commands depend on the tools used, but examples include using curl to send crafted requests or using intrusion detection systems (IDS) with custom rules to detect such exploit attempts. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Discontinuing use of the affected Linksys range extender models or isolating them from the network to prevent remote exploitation. 2) Since no vendor patch or fix is available, consider replacing the vulnerable devices with non-affected models. 3) Implement network-level protections such as firewall rules to block access to the /goform/ipRangeBlockManageRule endpoint or restrict management interface access to trusted hosts only. 4) Monitor network traffic for exploit attempts and respond accordingly. 5) Stay updated on any future vendor advisories or patches. [1]