Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
tesseract-ocr/tesseract
main @ 8eeeedd
17
Fixes
2
CVEs
HIGH
Peak severity
33.3%
Coverage
Highlights
Memory Corruption: 3 prior fixes. Scrutinize any change in this area.
src/classify/intmatcher.cpp: most-fixed (3 issues). Treat as high-risk during review.
9 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns
The bug types that recur here, drawn from past fixes, not open vulnerabilities.
Memory Corruption: The integer matcher utilizes multi-dimensional feature-evidence tables that are highly susceptible to out-of-bounds reads and writes. Failure to clamp ProtoIndex arrays to MAX_PROTO_INDEX and restrict configurations to MAX_NUM_CONFIGS can allow attackers to corrupt process memory during classification.
Memory Corruption: TFile's read and write functions are vulnerable to integer overflows when computing memory chunk allocations for buffer deserialization, which leads to heap overflows during subsequent memcpy operations.
Use After Free: Lack of explicit ownership semantics for layout blob objects yields critical use-after-free conditions. When structural elements are freed globally but references remain locally, downstream OCR operations trigger wild pointer dereferences.