Cyber Resilience

CVE-2025-8168

Memory Safety in Dlink Dir-513 Firmware 1.10

Public PoCMemory Safety
Published
25 July 2025
Modified
17 June 2026
Patch / advisory
CVSS Score v4 7.4
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.015 72th percentile
Risk Priority 41 floored blend · peak EPSS

Summary

CVE-2025-8168 is a high-severity Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) vulnerability in Dlink Dir-513. Its CVSS base score is 7.4 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 28% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

A vulnerability rated critical has been identified in the D-Link DIR-513 router running firmware version 1.10. It resides in the websAspInit function of the /goform/formSetWanPPPoE endpoint, where improper handling of the curTime argument triggers a buffer overflow. The affected device belongs to a product line that is no longer supported by the vendor, and the issue is tracked under CWE-119, CWE-120, and CWE-787.

Remote attackers with valid credentials can supply a crafted curTime value to the endpoint and trigger the overflow, resulting in potential impacts to confidentiality, integrity, and availability as reflected in the CVSS 7.4 vector. Publicly disclosed exploit code is available, enabling unauthenticated or low-privileged remote execution against exposed devices.

The vendor site and disclosure references confirm the product has reached end-of-life with no patches expected. The associated EPSS score remains flat at 0.0292 with no observed increase after publication.

EU & UK References

Vulnerability Data

A vulnerability was found in D-Link DIR-513 1.10. It has been rated as critical. Affected by this issue is the function websAspInit of the file /goform/formSetWanPPPoE. The manipulation of the argument curTime leads to buffer overflow. The attack may be…

more

launched remotely. The exploit has been disclosed to the public and may be used. This vulnerability only affects products that are no longer supported by the maintainer.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-10792Same product: Dlink Dir-513
CVE-2025-8169Same product: Dlink Dir-513
CVE-2026-4555Same product: Dlink Dir-513
CVE-2025-8184Same product: Dlink Dir-513
CVE-2026-4486Same product: Dlink Dir-513
CVE-2025-8159Same product: Dlink Dir-513
CVE-2026-5024Same product: Dlink Dir-513
CVE-2026-6012Same product: Dlink Dir-513
CVE-2026-6013Same product: Dlink Dir-513
CVE-2026-6014Same product: Dlink Dir-513

Affected Assets

dlink
dir-513 firmware
1.10

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V17.3.2
  • V5.2.1

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and analysis can find missing size checks before deployment.

Input validation directly enforces size checks before buffer copies.

Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.

Secure engineering principles require memory-safe design and coding that structurally avoids buffer-boundary violations.

Memory protection restricts exploitation impact of buffer overflows without eliminating the underlying coding flaw.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices (bounds checking, safe APIs, reviews) directly prevent this class of flaw.

ID.RA-01 partial match
prevents

Vulnerability scanning and code analysis directly surface buffer-boundary flaws.

ID.RA-08 partial match
prevents

Receiving and triaging vulnerability disclosures commonly includes buffer-related reports.

PR.AT-02 partial match
prevents

Developer training on secure coding reduces introduction of memory-buffer errors.

PR.PS-02 partial match
prevents

Patching replaces vulnerable code containing buffer-boundary defects.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

prevents

Secure coding directly requires bounds-checked memory operations, addressing the root cause of CWE-120.

finds

Security testing in development catches out-of-bounds accesses before release, covering most instances of the weakness.

prevents

Secure development lifecycle mandates memory-safety practices that directly prevent buffer-boundary violations.

prevents

Application security requirements can specify memory-safety rules, but do not prescribe implementation details.

prevents

Secure architecture and engineering principles include memory-safe design patterns that mitigate buffer overflows.

prevents

Change management can enforce review gates that catch unsafe memory operations before deployment.

References