-
* Several assertions in linearization were not always true; change them to run time errors * Handle a few cases of uninitialized objects * Handle pages with no contents when doing form operations * Handle invalid page tree nodes when traversing pages
-
* Create the seed corpus in the build directory * Don't assume all fuzzers share an options file
-
Now that there aren't any more...
-
This fixes cases of warning C4800 from msvc
-
This makes all integer type conversions that have potential data loss explicit with calls that do range checks and raise an exception. After this commit, qpdf builds with no warnings when -Wsign-conversion -Wconversion is used with gcc or clang or when -W3 -Wd4800 is used with MSVC. This significantly reduces the likelihood of potential crashes from bogus integer values. There are some parts of the code that take int when they should take size_t or an offset. Such places would make qpdf not support files with more than 2^31 of something that usually wouldn't be so large. In the event that such a file shows up and is valid, at least qpdf would raise an error in the right spot so the issue could be legitimately addressed rather than failing in some weird way because of a silent overflow condition.
-
This is the type we need for the underlying zlib implementation.
-
Change from unsigned long to int since we pass enumerated type values to this field.
-
Based on sizeof(size_t). Assumes 64 if not 32.
-
Bounding box X coordinates could be truncated, causing them to be off by a fraction of a point. This was most likely not visible, but it was still wrong.
-
Temporarily skip fuzz tests on Windows. There are Windows-specific failures to address later.
-
This is the set of files from the latest corpus of running the older fuzzer (qpdf_read_memory_fuzzer) at the time of adding the new fuzzer (qpdf_fuzzer) after running a merge operation to minimize the corpus.
-
There are more to handle, but this resolves an issue already caught by oss-fuzz.
-
On read, ignore /DecodeParms when empty list; on write, delete it. Some files have been found that include an empty list for /DecodeParms, but this is not technically compliant with the spec, and the only sensible interpretation is to treat it as if there are no decode parameters.