Files
harfbuzz/test/fuzzing/fonts
Behdad EsfahbodandClaude Opus 4.8 8f93b6d21b [layout] Charge GSUB/GPOS sanitize-time arrays to max_ops (#6631)
* [sanitize] Charge ChainRule backtrack/input/lookahead arrays to max_ops

ChainRule::sanitize() checks the length of each of its three arrays but
only sanitizes the trailing LookupRecord array, so it never charges
max_ops for the bytes it skipped over.  A table with many ChainRuleSet
offsets all pointing at one large ChainRule could therefore be
sanitized in time proportional to offsets x rule size, escaping the
sanitizer's work bound (restoring the accounting removed by 385896ff6).

Charge the skipped span (from this to the LookupRecord array) to
check_ops before sanitizing the records.  Adds a fuzzer regression
font.

Discovered by Anthropic's OSS Scanner, as vulnerability ANT-2026-EFNNHRHV.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* [GPOS] Charge zero-size ValueRecord arrays to the sanitizer op budget

When a ValueFormat is empty its records take no bytes, so
ValueFormat::sanitize_values() and PairPosFormat2::sanitize() pass
check_range() without charging max_ops for the records, while later
code (the subsetter, variation-index collection) still walks count
records.  A tiny table can thus declare a huge valueCount / class
matrix and cost the subsetter CPU out of proportion to its size.

Charge count ops when the record size / stride is zero, following the
918193ebf precedent.  Adds two fuzzer regression fonts.

Discovered by Anthropic's OSS Scanner, as vulnerability ANT-2026-HFGOLC64.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
2026-11-11 12:43:06 -06:00
..
2020-01-31 16:37:30 -05:00
2022-06-01 07:39:20 -06:00