Local memory corruption via oversized object-stack allocation
Published Jul 20, 2021 · Updated Aug 5, 2024
Heap-based buffer overflow in GNU Aspell 0.60.8 allows local users to corrupt memory through an oversized object-stack allocation. ObjStack::dup_top copies a string into a fixed-size chunk after the allocator creates a new chunk without verifying that the requested object fits. A low-privileged local process must reach StringMap::add through Config::lookup_list; the demonstrated consequence is an out-of-bounds heap write.
Summary
What happened
Heap-based buffer overflow in GNU Aspell 0.60.8 allows local users to corrupt memory through an oversized object-stack allocation. ObjStack::dup_top copies a string into a fixed-size chunk after the allocator creates a new chunk without verifying that the requested object fits. A low-privileged local process must reach StringMap::add through Config::lookup_list; the demonstrated consequence is an out-of-bounds heap write.
The record
- CVE
- CVE-2019-25051
- Published
- Jul 20, 2021
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 20, 2021CVE publishedPublication date reported by the CVE source.
- Aug 5, 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?
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.
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