CVE-2025-70229
Stack Buffer Overflow in D-Link DIR-513 via curTime Parameter
Publication date: 2026-03-05
Last updated on: 2026-03-06
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| dlink | dir-513_firmware | 1.10 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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?
CVE-2025-70229 is a stack buffer overflow vulnerability found in the D-Link DIR-513 router, specifically in firmware version v1.10. The vulnerability exists in the component handling the endpoint goform/formSchedule and is triggered via the curTime parameter.
The overflow occurs because the curTime input is passed to a sprintf function without adequate bounds checking, which leads to a stack buffer overflow condition.
An attacker can exploit this by sending an excessively long string in the curTime parameter to the /goform/formSchedule endpoint, potentially causing the overflow.
How can this vulnerability impact me? :
This vulnerability could potentially allow an attacker to execute arbitrary code on the affected device or cause a denial of service (DoS).
Exploitation could lead to unauthorized control over the router, disruption of network services, or compromise of network security.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability can be detected by monitoring HTTP POST requests to the endpoint /goform/formSchedule on the D-Link DIR-513 router firmware v1.10. Specifically, look for unusually long or malformed values in the curTime parameter, which triggers the stack buffer overflow.'}, {'type': 'paragraph', 'content': 'A practical detection method is to capture network traffic and filter for POST requests targeting /goform/formSchedule, then inspect the curTime parameter length.'}, {'type': 'list_item', 'content': 'Use a network packet capture tool like tcpdump or Wireshark to capture HTTP POST requests to /goform/formSchedule.'}, {'type': 'list_item', 'content': "Example tcpdump command to capture relevant traffic: tcpdump -i <interface> -A 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)' | grep 'POST /goform/formSchedule'"}, {'type': 'list_item', 'content': 'Inspect captured POST requests for the curTime parameter and check if its value length exceeds normal expected sizes.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting access to the vulnerable endpoint /goform/formSchedule on the affected D-Link DIR-513 router to trusted users only.
Additionally, monitor and block HTTP POST requests with suspiciously long curTime parameter values that could trigger the overflow.
If possible, update the router firmware to a version that addresses this vulnerability or apply vendor-provided patches.
As a temporary measure, consider disabling remote management features or restricting management access to the local network.