CVE-2025-70232
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 · uneditedStack buffer overflow vulnerability in D-Link DIR-513 v1.10 via the curTime parameter to goform/formSetMACFilter.
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 · high confidenceStack buffer overflow vulnerability in D-Link DIR-513 v1.10 router firmware. The curTime parameter in the /goform/formSetMACFilter endpoint does not properly validate input length before copying to a fixed-size stack buffer, allowing an attacker to overwrite return addresses and potentially execute arbitrary code remotely.
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= 1.10CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is D-Link DIR-513Access the router web interface (typically at 192.168.0.1) and check the device info/status page, or SSH to the device and run 'cat /proc/cpuinfo' or check the model number in the system logAffected if Device is not a D-Link DIR-513 unit
-
Check firmware version is 1.10In the router web interface, navigate to Status or Management > Firmware Upgrade page to view the current firmware version, or via CLI run 'nvram get firmware_version' or check /etc/versionAffected if Firmware version equals 1.10
-
Verify the /goform/formSetMACFilter endpoint existsAttempt to access http://<router-ip>/goform/formSetMACFilter via HTTP request (no authentication check shown in advisory) or inspect the web server binary for the formSetMACFilter handlerAffected if Endpoint responds or handler code is present in the firmware
-
Check if remote management is enabledIn the router web interface under Advanced > Remote Management, verify if remote access (WAN) is permitted on HTTP/HTTPS ports, or via CLI check 'nvram get remote_management' or iptables rules on WAN interfaceAffected if Remote management is enabled and the device is exposed to WAN
A defender is affected if they are running D-Link DIR-513 firmware version 1.10 with the formSetMACFilter endpoint accessible, especially if remote management is enabled.
Generated from the published advisory. Verify against your own configuration.
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 · scopedReplace end-of-life D-Link DIR-513 devices with supported hardware; if immediate replacement is not feasible, disable remote management access and segment the device on an isolated VLAN to reduce attack surface.
- This CVE lacks publicly available fixed version, patch, or upgrade path information in the reference sources.
- Check D-Link's support pages (www.dlink.com, www.dlink.com.cn) periodically for firmware updates for the DIR-513 model.
- If no firmware update is available, consider replacing the affected device with a currently supported model.
- Monitor D-Link security advisories for future patches.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-70232 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-70232 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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