CyberRota Analysis
AI-GeneratedTesseract OCR engine versions 5.5.3 and earlier are vulnerable due to improper handling of unichar counts, which can lead to unchecked indexing into the unichars vector. This flaw may result in heap corruption, crashes, or potentially exploitable controlled corruption during initialization. Organizations using Tesseract for OCR tasks should prioritize addressing this vulnerability, especially those in security-sensitive environments, as no fix is currently available.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Tesseract is an open source OCR engine. In version 5.5.3 and earlier, UNICHARSET::load_via_fgets in src/ccutil/unicharset.cpp trusts the declared unichar count as a loop bound and uses id as an unchecked index into the unichars vector. unichar_insert_backwards_compatible can leave the vector unchanged for an empty, duplicate, or already-encodable representation, causing id to become larger than unichars.size(). Subsequent set_* calls and the write to unichars[id].properties.enabled then write UNICHAR_PROPERTIES beyond the vector during initialization in both the default LSTM and legacy engines, causing heap corruption, a crash, or potentially controlled corruption. No fixed release is available as of this review.