I saw a claim that a Brotli vulnerability could reach systems through WOFF2 fonts, including servers that process them. How should I assess the risk without assuming every font request is dangerous?
Could a Brotli vulnerability affect WOFF2 web fonts too?
Answers
Start with the specific vulnerability advisory and the affected decoder versions. WOFF2 uses Brotli compression, so a vulnerable decoder could matter if it processes a crafted font. But that connection alone does not establish that every WOFF2 implementation is exploitable.
Check which library and version each font-processing component actually uses, including bundled copies. Updating a system Brotli package may not update a copy compiled into another library. The source claim points to a bundled copy in one WOFF2 build, but the affected status and available fix need confirmation from the relevant maintainers or advisory.
Reply to this answer
Trace the actual path the font takes. A server that stores and sends a WOFF2 file is not necessarily decompressing it. A font conversion tool, preview generator, scanner, or other component that parses the font is a more relevant place to check.
On the client side, exposure depends on the decoder used by the application displaying the font. Neither path should be assumed vulnerable just because the file is served over the web.
Reply to this answer
Blocking HTTP requests with Brotli content encoding is not the same thing as blocking a WOFF2 font. The font can contain Brotli-compressed data regardless of whether HTTP content encoding is used.
If an affected font decoder is confirmed, consider restricting untrusted fonts from reaching that processing step while a fix is deployed. Check the effect on legitimate font traffic before applying a broad filter.
Reply to this answer
I would treat the dramatic claims with skepticism. The discussion does not establish that a firewall must crash, that clients must crash, or that malicious fonts are already sitting in buckets. Those are separate claims that need evidence, not conclusions from the use of Brotli.
Reply to this answer
Add your answer
Answers are reviewed before publication.
6v!brindlewinder_739:
Does a Unicode decode error in middleware show that the font was decompressed?
_g64!drainwhistle.3:
No. It shows that something tried to interpret bytes as text, not that it decoded the WOFF2 contents with Brotli.