Root code execution via device-name buffer overflow
Published May 3, 2024 · Updated Sep 18, 2024
Stack-based buffer overflow in D-Link DAP-2622 1.00 and earlier allows network-adjacent attackers to execute arbitrary code without authentication. The DDP Set Device Info handler copies a user-supplied device name into a fixed-length stack buffer without first validating its length. A crafted adjacent-network request corrupts memory and executes attacker-controlled code in the service's root context.
Summary
What happened
Stack-based buffer overflow in D-Link DAP-2622 1.00 and earlier allows network-adjacent attackers to execute arbitrary code without authentication. The DDP Set Device Info handler copies a user-supplied device name into a fixed-length stack buffer without first validating its length. A crafted adjacent-network request corrupts memory and executes attacker-controlled code in the service's root context.
The record
- CVE
- CVE-2023-37312
- Published
- May 3, 2024
- Updated
- Sep 18, 2024
- Vendor
- D-Link
- Product
- DAP-2622 Firmware
- Classifications
- CWE-121, CWE-787, T1210
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 3, 2024CVE publishedPublication date reported by the CVE source.
- Sep 18, 2024Record 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=0 <=1.00
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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