CVE-2025-15193
Remote Buffer Overflow in D-Link DWR-M920 sub_423848 Function
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 firmware version 1.1.50. It involves a buffer overflow in the function sub_423848 within the /boafrm/formParentControl file. The issue arises when the argument 'submit-url' is manipulated, allowing an attacker to remotely exploit the buffer overflow.
How can this vulnerability impact me? :
The vulnerability can be exploited remotely to cause a buffer overflow, which may lead to unauthorized control or disruption of the affected device. This can result in compromised device integrity, potential denial of service, or unauthorized access.
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 vulnerable endpoint /boafrm/formParentControl, specifically looking for manipulation of the submit-url argument that could trigger the buffer overflow. Since the exploit is publicly available, you can use network traffic inspection tools like tcpdump or Wireshark to capture and analyze suspicious requests targeting this path. Additionally, using curl or similar HTTP clients to test the endpoint with oversized submit-url parameters may help confirm vulnerability presence. Example command to test manually: curl -X POST 'http://<device-ip>/boafrm/formParentControl' -d 'submit-url=<very long string>'. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Currently, no known mitigations or countermeasures exist for this vulnerability. The recommended immediate step is to replace the affected product or update the firmware to a version that is not vulnerable, if available. Until a patch or fix is released, restricting remote access to the device and monitoring for exploit attempts is advised to reduce risk. [1]