Memory corruption via oversized circular-buffer copy
Published Aug 24, 2021 · Updated Aug 3, 2024
Heap-based buffer overflow in ok-file-formats through 2021-04-29 allows attackers to corrupt memory by parsing a crafted CSV file. On the demonstrated path, ok_csv_circular_buffer_read writes 181 CSV-derived bytes into a 64-byte heap allocation without limiting the write to the remaining capacity. A consuming application must parse the crafted file; the published reproducer triggers an AddressSanitizer abort, while code execution remains unproven.
Summary
What happened
Heap-based buffer overflow in ok-file-formats through 2021-04-29 allows attackers to corrupt memory by parsing a crafted CSV file. On the demonstrated path, ok_csv_circular_buffer_read writes 181 CSV-derived bytes into a 64-byte heap allocation without limiting the write to the remaining capacity. A consuming application must parse the crafted file; the published reproducer triggers an AddressSanitizer abort, while code execution remains unproven.
The record
- CVE
- CVE-2021-32263
- Published
- Aug 24, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 24, 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?
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
- poc.csv heap-overflow reproducerproof of concept · demonstrated
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