Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.0.28, 3.0.0 PDFBox
-
None
Description
At 2 places the Type1Parser has a loop with a negated condition on the next token to be read. The loops simply advances to the next token without checking the token to be null, which may happen if the font is corrupted/shortened. If this occurs the parser is stuck in the loops. This happens to me for one of the loops with a file which however cannot be shared. The 2nd loop was found by scanning the code for similar problems.