CVE-2025-15189
Remote Buffer Overflow in D-Link DWR-M920 Router Firmware
Publication date: 2025-12-29
Last updated on: 2025-12-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| d-link | dwr-m920 | 1.1.50 |
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-120 | The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the D-Link DWR-M920 device up to version 1.1.50. It affects a specific function (sub_464794) in the file /boafrm/formDefRoute. The issue arises from improper handling of the 'submit-url' argument, which can be manipulated to cause a buffer overflow. This means an attacker can remotely exploit this flaw to potentially execute arbitrary code or cause the device to crash.
How can this vulnerability impact me? :
The vulnerability can be exploited remotely to cause a buffer overflow, which may allow an attacker to execute arbitrary code, disrupt device functionality, or cause a denial of service. This can lead to unauthorized access, loss of control over the device, or interruption of network services relying on the affected device.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection can be performed by monitoring HTTP requests to the /boafrm/formDefRoute endpoint for unusual or oversized submit-url parameters that may indicate exploitation attempts. Since the exploit is publicly available, you can use network traffic analysis tools like tcpdump or Wireshark to capture and inspect such requests. For example, using tcpdump: tcpdump -i <interface> -A 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)' and then filtering for /boafrm/formDefRoute in the HTTP payload. Additionally, you can use curl or wget to test the endpoint manually by sending crafted requests with large submit-url parameters to see if the device responds abnormally. However, no specific detection commands are provided in the resources. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected product or upgrading the firmware to a version beyond 1.1.50 if available. Since no known mitigations or countermeasures have been identified, it is recommended to restrict remote access to the device, disable unnecessary services, and monitor for exploitation attempts. Applying network-level protections such as firewall rules to block access to the /boafrm/formDefRoute endpoint can also help reduce risk until a patch or replacement is implemented. [2]