The edge-work estimator cast the result of the y-coordinate subtraction to int64_t, after the subtraction had already happened in int32_t. An edge spanning the clamped coordinate range could therefore overflow before the work was capped to the surface height. Widen both operands before subtracting, matching the existing edge slope calculation, and add the minimized OSS-Fuzz reproducer to the fuzz corpus. Fixes: https://oss-fuzz.com/testcase-detail/5773854015029248 Assisted-by: OpenAI Codex <noreply@openai.com>
Security Fuzzers
To build the fuzzers with libFuzzer to perform actual fuzzing, build with:
CXX=clang++ CXXFLAGS="-fsanitize=address,fuzzer-no-link" meson fuzzbuild --default-library=static -Dfuzzer_ldflags="-fsanitize=address,fuzzer"
ninja -Cfuzzbuild
Then, run the fuzzer like this:
fuzzbuild/test/fuzzing/hb-{shape,raster,vector,subset,repacker,depend}-fuzzer [-max_len=2048] [CORPUS_DIR]
Where max_len specifies the maximal length of font files to handle. The smaller the faster.
Note: The depend fuzzer requires -Ddepend_api=true meson option.
For more details consult the following locations:
Depend Closure Parity Test
The hb-depend-closure-parity test is distinct from the security fuzzers.
While security fuzzers test robustness against malformed input, the closure
parity test validates correctness by emulating the glyph closure calculation
used for subsetting with one generated from the dependency graph to avoid
implementation divergence. It should only be run on valid fonts.