Service interruption via unbounded sprintf write
Published Mar 3, 2026 · Updated Mar 3, 2026
Stack buffer overflow in D-Link DIR-513 1.10 allows remote attackers to interrupt service via a crafted curTime form parameter. The handler passes curTime through v13 to sprintf, which writes the attacker-controlled value to a stack buffer without a length bound. The endpoint requires no privileges or user interaction, and CISA bounds the assessed effect to reduced availability rather than code execution or data access.
Summary
What happened
Stack buffer overflow in D-Link DIR-513 1.10 allows remote attackers to interrupt service via a crafted curTime form parameter. The handler passes curTime through v13 to sprintf, which writes the attacker-controlled value to a stack buffer without a length bound. The endpoint requires no privileges or user interaction, and CISA bounds the assessed effect to reduced availability rather than code execution or data access.
The record
- CVE
- CVE-2025-70236
- Published
- Mar 3, 2026
- Updated
- Mar 3, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, CWE-121, T1190, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 3, 2026CVE publishedPublication date reported by the CVE source.
- Mar 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- akuma-QAQ DIR-513 curTime proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo