Application crash via out-of-bounds stack read
Published Nov 17, 2021 · Updated Aug 3, 2024
Stack buffer underflow in GOCR through 0.53-20200802 allows local users to crash the application by processing a crafted image. The try_to_divide_boxes function reads four bytes from immediately before its ci stack array while processing the supplied image. A user or automated workflow must cause GOCR to process the image; the demonstrated result is AddressSanitizer termination, not proven code execution.
Summary
What happened
Stack buffer underflow in GOCR through 0.53-20200802 allows local users to crash the application by processing a crafted image. The try_to_divide_boxes function reads four bytes from immediately before its ci stack array while processing the supplied image. A user or automated workflow must cause GOCR to process the image; the demonstrated result is AddressSanitizer termination, not proven code execution.
The record
- CVE
- CVE-2021-33481
- Published
- Nov 17, 2021
- Updated
- Aug 3, 2024
- Vendor
- GOCR Project
- Product
- GOCR
- Classifications
- CWE-787, CWE-119, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 17, 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=gocr 0.53-20200802
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.
Weakness, pattern, technique
Public exploit references
- stack-overflow-try_to_divide_boxes-pgm2asc-2648.zipproof 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