Memory corruption via oversized Authorization header
Published Mar 3, 2025 · Updated Mar 4, 2025
Stack-based buffer overflow in the HTTP Header Handler in D-Link DAP-1562 1.10 allows remote attackers to corrupt memory via Authorization. The http_request_parse function fails to enforce stack-buffer bounds while parsing an oversized Authorization header. No authentication or user interaction is required; the published record does not establish whether the overflow only crashes the device or permits code execution.
Summary
What happened
Stack-based buffer overflow in the HTTP Header Handler in D-Link DAP-1562 1.10 allows remote attackers to corrupt memory via Authorization. The http_request_parse function fails to enforce stack-buffer bounds while parsing an oversized Authorization header. No authentication or user interaction is required; the published record does not establish whether the overflow only crashes the device or permits code execution.
The record
- CVE
- CVE-2025-1876
- Published
- Mar 3, 2025
- Updated
- Mar 4, 2025
- Vendor
- D-Link
- Product
- DAP-1562
- Classifications
- CWE-787, CWE-121, CWE-119, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 3, 2025CVE publishedPublication date reported by the CVE source.
- Mar 4, 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=1.10
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
- DAP-1562 http_request_parse proof of conceptproof of concept · demonstrated
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