Memory corruption via hi_up stack overflow
Published Sep 20, 2023 · Updated Sep 25, 2024
Stack-based buffer overflow in D-Link DI-7200GV2.E1 21.04.09E1 allows remote attackers to corrupt memory via the hi_up parameter. The public record identifies qos_ext.asp as the vulnerable function and hi_up as the triggering input, but it does not disclose the precise unsafe memory operation. No authentication or user interaction is required, while the record does not establish whether exploitation results in a crash, code execution, or another concrete outcome.
Summary
What happened
Stack-based buffer overflow in D-Link DI-7200GV2.E1 21.04.09E1 allows remote attackers to corrupt memory via the hi_up parameter. The public record identifies qos_ext.asp as the vulnerable function and hi_up as the triggering input, but it does not disclose the precise unsafe memory operation. No authentication or user interaction is required, while the record does not establish whether exploitation results in a crash, code execution, or another concrete outcome.
The record
- CVE
- CVE-2023-43201
- Published
- Sep 20, 2023
- Updated
- Sep 25, 2024
- Vendor
- D-Link
- Product
- DI-7200GV2
- Classifications
- CWE-787
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 20, 2023CVE publishedPublication date reported by the CVE source.
- Sep 25, 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=v21.04.09e1
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