tesseract-ocr/tesseract

Bugs reported by OSS-Fuzz

Open

#2629 opened on Aug 28, 2019

View on GitHub
 (11 comments) (0 reactions) (0 assignees)C++ (74,090 stars) (10,622 forks)batch import
bughelp wanted

Description

There are currently several open issues which were detected by OSS-Fuzz and which I could not fix in time: https://bugs.chromium.org/p/oss-fuzz/issues/list?q=Proj%3Dtesseract-ocr. One of them is classified as a security bug.

Contributor guide

Tech stack
cpp
Domain
security
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
Familiarity with Tesseract codebaseOSS Fuzz experienceSecurity debuggingC++ debugging
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
The issue is a meta issue linking to OSS Fuzz bug reports. First, review the linked list and identify still open bugs. Choose a specific bug, e.g., the security one, and analyze the fuzzing test case. Examine relevant Tesseract source files, likely in the core or training directories, to locate the vulnerability. Fix the bug and add a regression test. Check issue comments for maintainer guidance on priority.