CVE-2025-15190
Remote Stack-Based Buffer Overflow in D-Link DWR-M920 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-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-based buffer overflow in the D-Link DWR-M920 device (up to firmware version 1.1.50). It occurs in the function sub_42261C within the file /boafrm/formFilter when the argument ip6addr is manipulated. This flaw allows an attacker to remotely exploit the device by sending specially crafted input that overflows the stack buffer, potentially leading to arbitrary code execution or system compromise.
How can this vulnerability impact me? :
The vulnerability can allow a remote attacker to execute arbitrary code or cause a denial of service on the affected D-Link DWR-M920 device. This could lead to unauthorized access, disruption of network services, or compromise of the device's integrity and confidentiality.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected D-Link DWR-M920 device or firmware versions up to 1.1.50, as no known mitigations or countermeasures have been documented. Since the vulnerability can be exploited remotely without authentication, discontinuing use of the vulnerable firmware or device is recommended to prevent exploitation. [3]