A format 1 Encoding can give codes to more than 255 glyphs, since codes may repeat across ranges. When the subset keeps more than 255 of those glyphs, as with retain-gids, plan_subset_encoding() hit assert (subset_enc_num_codes <= 0xFF). Choose format 0 only when it can hold the codes, and fail cleanly in the format 1 serializer instead of truncating nRanges past 255. Add a test font whose format 1 Encoding covers 768 glyphs, and the reporter's font to the fuzzing corpus. Fixes: https://github.com/harfbuzz/harfbuzz/issues/6031 Assisted-by: Claude Assisted-by: OpenAI Codex
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.