CVE-2025-60333
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-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 overflow in the wepkey2 parameter within the setWiFiMultipleConfig function of TOTOLINK N600R firmware version 4.3.0cu.7866_B20220506. An attacker can exploit this by sending a specially crafted input to cause the stack overflow. [1]
How can this vulnerability impact me? :
Exploiting this vulnerability can cause a Denial of Service (DoS) condition, meaning the affected device may crash or become unresponsive, disrupting normal network operations.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection of this vulnerability involves monitoring for attempts to exploit the stack overflow in the wepkey2 parameter of the setWiFiMultipleConfig function. Since the vulnerability is triggered by crafted input causing a Denial of Service, you can look for unusual or malformed packets targeting the WiFi configuration interface of TOTOLINK N600R devices. Specific commands are not provided in the resources, but reviewing logs for crashes or service interruptions related to WiFi configuration changes may help. Additionally, analyzing network traffic for suspicious payloads targeting the wepkey2 parameter could be useful. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the WiFi configuration interface to trusted users only, disabling remote configuration if possible, and monitoring for unusual activity. Since the vulnerability is a stack overflow triggered by crafted input, applying any available firmware updates or patches from TOTOLINK addressing this issue is recommended once available. In the absence of patches, limiting network exposure and access controls are the best immediate measures. [1]