CVE-2025-60335
BaseFortify
Publication date: 2025-10-22
Last updated on: 2025-10-24
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| totolink | n600r_firmware | 4.3.0cu.7866_b20220506 |
| totolink | n600r | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-476 | The product dereferences a pointer that it expects to be valid but is NULL. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a NULL pointer dereference in the main function of TOTOLINK N600R v4.3.0cu.7866_B20220506. It allows attackers to cause a Denial of Service (DoS) by sending a specially crafted HTTP request that triggers the NULL pointer dereference, leading the device to crash or become unresponsive.
How can this vulnerability impact me? :
The impact of this vulnerability is a Denial of Service (DoS) condition on the affected TOTOLINK N600R device. An attacker can exploit this by sending a crafted HTTP request, causing the device to crash or stop functioning properly, which can disrupt network connectivity and availability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending crafted HTTP requests that trigger the NULL pointer dereference in the TOTOLINK N600R device. Specific commands or proof-of-concept scripts to test this are available in the linked GitHub resource, which contains details on how to reproduce the issue via HTTP requests targeting the main function. You can use tools like curl or custom scripts to send these crafted HTTP requests to the device and observe if it causes a Denial of Service. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the TOTOLINK N600R device's HTTP interface from untrusted networks, such as by using firewall rules or network segmentation. Additionally, monitoring for unusual HTTP requests and applying any available firmware updates from the vendor once released are recommended. Until a patch is available, limiting exposure of the device to potentially malicious HTTP traffic is the best immediate action. [1]