Local process corruption via out-of-bounds global writes
Published Jun 16, 2021 · Updated Jul 9, 2026
Out-of-bounds writes in D-Link DIR-2640-US firmware 1.01B04 allow local users to corrupt process memory and crash services. The affected processes write beyond buffer bounds into global variables in their .bss sections; their names and input paths are undisclosed. An ordinary local account is required; successful writes alter process state or terminate the affected process.
Summary
What happened
Out-of-bounds writes in D-Link DIR-2640-US firmware 1.01B04 allow local users to corrupt process memory and crash services. The affected processes write beyond buffer bounds into global variables in their .bss sections; their names and input paths are undisclosed. An ordinary local account is required; successful writes alter process state or terminate the affected process.
The record
- CVE
- CVE-2021-34201
- Published
- Jun 16, 2021
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 16, 2021CVE publishedPublication date reported by the CVE source.
- Jul 9, 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.
Public exploit references
- CVE-2021-34201 research artifactproof 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