Memory corruption via unchecked dynamic symbol bounds
Published Apr 29, 2021 · Updated Aug 3, 2024
Out-of-bounds write in readelf in The GnuPG Project GNU Binutils 2.35.2 allows attackers to corrupt memory via a crafted file. The print_dynamic_symbol routine writes attacker-controlled symbol data without adequate bounds checking, causing a stack buffer overflow and arbitrary out-of-bounds write. A victim must be persuaded to run readelf on the file, and exploitation can crash the utility or enable code execution with the victim's local privileges.
Summary
What happened
Out-of-bounds write in readelf in The GnuPG Project GNU Binutils 2.35.2 allows attackers to corrupt memory via a crafted file. The print_dynamic_symbol routine writes attacker-controlled symbol data without adequate bounds checking, causing a stack buffer overflow and arbitrary out-of-bounds write. A victim must be persuaded to run readelf on the file, and exploitation can crash the utility or enable code execution with the victim's local privileges.
The record
- CVE
- CVE-2021-20294
- Published
- Apr 29, 2021
- Updated
- Aug 3, 2024
- Vendor
- The GnuPG Project
- Product
- GNU Binutils
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 29, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=binutils 2.35.2
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.
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