Process crash via freed box dereference
Published Nov 17, 2021 · Updated Aug 3, 2024
Use-after-free in GOCR 0.53-20200802 allows context-dependent attackers to crash the OCR process via crafted image input. In pgm2asc.c, context_correction reads a box field after free_box releases the heap allocation containing it. Exploitation requires a user or local workflow to run GOCR in mode 4 on attacker-supplied input, causing the process to abort.
Summary
What happened
Use-after-free in GOCR 0.53-20200802 allows context-dependent attackers to crash the OCR process via crafted image input. In pgm2asc.c, context_correction reads a box field after free_box releases the heap allocation containing it. Exploitation requires a user or local workflow to run GOCR in mode 4 on attacker-supplied input, causing the process to abort.
The record
- CVE
- CVE-2021-33480
- Published
- Nov 17, 2021
- Updated
- Aug 3, 2024
- Vendor
- GOCR Project
- Product
- GOCR
- Classifications
- CWE-416, 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.
Public exploit references
- context_correction line 2817 reproducerproof of concept · demonstrated
- context_correction line 2857 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