CVE-2025-45057
Buffer Overflow in D-Link DI-8300 Causes Denial of Service
Publication date: 2026-04-08
Last updated on: 2026-04-10
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| dlink | di-8300_firmware | 16.07.26a1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify any direct impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA.
Can you explain this vulnerability to me?
CVE-2025-45057 is a buffer overflow vulnerability found in the D-Link DI-8300 router firmware version 16.07.26A1.
The flaw exists specifically in the function ip_position_asp, where an attacker can trigger a stack overflow by supplying an excessively long ip parameter.
Exploiting this vulnerability results in a denial of service (DoS) condition, causing the device to crash or become unresponsive.
How can this vulnerability impact me? :
This vulnerability can impact you by causing a Denial of Service (DoS) on the affected D-Link DI-8300 router.
An attacker can exploit the buffer overflow by sending a crafted input to the ip parameter, which can crash the device or make it unresponsive.
As a result, network connectivity and availability provided by the router may be disrupted.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring for unusual crashes or unresponsiveness of the D-Link DI-8300 router, especially when receiving network traffic containing the ip parameter in requests to the ip_position_asp function.
Since the vulnerability is triggered by a crafted input with an excessively long ip parameter, you can attempt to detect it by sending test requests with long ip parameters to the device and observing if it causes a crash or denial of service.
No specific detection commands are provided in the available resources.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps are not explicitly detailed in the provided resources.
General best practices include limiting access to the affected device from untrusted networks, monitoring for unusual device behavior, and applying any available firmware updates or patches from the vendor.