dbcve.org
Di 8300 FirmwareOperating system · Dlink

CVE-2025-45057

HIGH · 7.5 CVSS v3.1 Published 2026-04-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
D-Link DI-8300 v16.07.26A1 was discovered to contain a buffer overflow via the ip parameter in the ip_position_asp function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted input.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A buffer overflow vulnerability exists in the ip_position_asp function of D-Link DI-8300 router firmware v16.07.26A1. The vulnerability is triggered via the ip parameter, allowing attackers to send crafted input that overflows a buffer, leading to Denial of Service. The CVSS 7.5 score indicates high severity due to the potential for service disruption.

MitigationContact D-Link support to verify if a firmware patch is available; if not, consider network segmentation to limit exposure and implement input validation at upstream network devices. For long-term remediation, the ip_position_asp function must be rewritten with proper bounds checking on the ip parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Di 8300 FirmwareOperating system
Affected:= 16.07.26a1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the router admin interface or check the device label to confirm the model is D-Link DI-8300
    Affected if Device is not a D-Link DI-8300 model, then not affected
  2. Check the firmware version
    Log into the router web interface and navigate to Status or System Info page to view the firmware version, or use command line: cat /proc/version or grep the firmware file
    Affected if Firmware version is exactly 16.07.26A1 - this is the only affected version listed
  3. Verify the ip_position_asp function is accessible
    Check if the router web interface is accessible and examine HTTP requests to /ip_position.asp or similar endpoints that would invoke the ip_position_asp function
    Affected if The web management interface is enabled and exposed, and the ip_position_asp endpoint exists and accepts ip parameter input
  4. Look for signs of exploitation or crash
    Check router system logs for unexpected reboots, crashes, or buffer overflow indicators. Review web server logs for suspicious requests with unusually long ip parameter values
    Affected if Device exhibits unexplained crashes, DoS symptoms, or logs show abnormal ip parameter patterns

A user is affected only if they have a D-Link DI-8300 router running firmware version 16.07.26A1 with the web management interface enabled and the ip_position_asp function exposed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Contact D-Link support to verify if a firmware patch is available; if not, consider network segmentation to limit exposure and implement input validation at upstream network devices. For long-term remediation, the ip_position_asp function must be rewritten with proper bounds checking on the ip parameter.

Recommended fix Moderate confidence

Latest available DI-8300 firmware from D-Link official support channels (check www.dlink.com.cn or www.dlink.com for version newer than 16.07.26a1)

  1. 1. Visit the official D-Link support website (www.dlink.com or www.dlink.com.cn) and navigate to the DI-8300 product support page.
  2. 2. Check the firmware download section for any available updates newer than version 16.07.26a1.
  3. 3. Download the latest available firmware version from D-Link's official site.
  4. 4. Access the DI-8300 router web management interface.
  5. 5. Navigate to the firmware upgrade or system settings section.
  6. 6. Upload and apply the new firmware file, ensuring power is not interrupted during the process.
  7. 7. After the router reboots, verify the new firmware version is installed correctly.
  8. 8. Test that the ip_position_asp function and related network features work properly after the upgrade.
Caveat Firmware updates may reset configuration to defaults; backup current settings before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Di 8300 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-45057 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-45057 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data