Memory corruption via curTime buffer overflow
Published May 9, 2025 · Updated May 9, 2025
Buffer overflow in D-Link DIR-619L 2.04B04 allows remote authenticated users to corrupt memory through the formSetEasy_Wizard curTime argument. Public sources identify the handler and argument but do not disclose the copy operation or destination buffer that fails to enforce bounds. Management-interface access is required, and public sources do not establish whether the corruption causes a crash or attacker-controlled code execution.
Summary
What happened
Buffer overflow in D-Link DIR-619L 2.04B04 allows remote authenticated users to corrupt memory through the formSetEasy_Wizard curTime argument. Public sources identify the handler and argument but do not disclose the copy operation or destination buffer that fails to enforce bounds. Management-interface access is required, and public sources do not establish whether the corruption causes a crash or attacker-controlled code execution.
The record
- CVE
- CVE-2025-4450
- Published
- May 9, 2025
- Updated
- May 9, 2025
- Vendor
- D-Link
- Product
- DIR-619L
- Classifications
- CWE-120, CWE-119, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 9, 2025CVE publishedPublication date reported by the CVE source.
- May 9, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.04B04
What conditions does exploitation require?
What is affected?
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
No public exploit references are available in this record.
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