OpenSystemsDevelopment / qpdf

Fixes oss-fuzz case 394129398.

Issue arose from chaining multiple runlength filters and inflating a
compressed stream of ~100 bytes to several gigabytes.

There is no obvious fix without imposing an arbitrary implementation limit
and therefore potentially excluding valid PDF files.

Check for direct outline items.

Fixes oss-fuzz case 	389339260.

Fixes oss-fuzz cases 376305073, 389974979 and 391974927.

This reverts commit 0e92cf6bf399249c603c3d0212e898fd29e71fcd, reversing
changes made to 7d34b89a69e8e89c098dd373442f7df809c28eff.

Tokens longer than the target cannot be a match and therefore there is no
need to read to the end of token.

Fixes fuzz issue 71689.

Ensure QPDF m->all_pages and invalid_page_found are reset if
getAllPagesInternal throws an exception.

Fixes fuzz case 71624.

Buffer output locally.
Add qpdf_fuzzer test case.

Also, add additional qpdf_fuzzer test case.

Throw damagedFile if max_warnings is exceeded. Change qpdf_fuzzer warnings limit to
limit to 500.

Try a  limit of 50MB. For very large limits processing time before
damage is encountered may exceed oss-fuzz limits.
Add further test cases.

Reject non-dictionary Page and Pages objects.

Also add additional qpdf_fuzzer test cases.

Add test case for oss-fuzz 15471 and 69977a

Fixes oss-fuzz 70055

As a rule, we should avoid conditional compilation is it always causes
code paths that are sometimes not even seen lexically by the compiler.
Also, we want the actual code being fuzzed to be as close as possible
to the real code. Conditional compilation is suitable to handle
underlying system differences.

Instead, favor configuration using callbacks or other methods that can
be triggered in the places where they need to be exercised.

Add extra fuzz test case and amend memory limit for Pl_DCT.

Also, add diagnostic messages in qpdf_fuzzer and additional fuzz test case.

Fix #1170

In PL_DCT add option to limit the size of uncompressed corrupt data

In QPDF::read_xrefEntry add buffer overflow test for first eol character.
Overlong f1 or f2 entries consisting only of zeros could cause a buffer
overflow.

Add fuzz testcase 69913.

Also, apply limit in dct_fuzzer

Also add new fuzz test case.