CVE-2022-35108

What it actually does

A segmentation violation in DCTStream::getChar() at Stream.cc triggers a crash when the parser processes malformed DCT-encoded streams inside SWF files.

Why it matters to the business

Work that depends on SWFTools to inspect or convert Flash files can be interrupted by unexpected crashes when untrusted inputs are supplied.

How an attack unfolds

An attacker builds an SWF containing a crafted DCT stream, then convinces a target to open the file with any affected SWFTools binary; the parser dereferences invalid memory and the process terminates.

How to fix it

Replace the vulnerable SWFTools installation with a version that resolves the Stream.cc flaw; if no patched release exists, restrict the tool to trusted inputs only.

How to confirm the fix worked

Run the affected binaries against a minimal crashing SWF sample and confirm the process no longer terminates with a segmentation violation; also verify the installed binary is newer than commit 772e55a2.

Typical attack path

1. Create SWF embedding malformed DCT data
2. Deliver the file via email, web download or shared storage
3. Victim invokes an SWFTools utility on the file
4. DCTStream::getChar triggers segmentation fault and the process exits

How to detect it

Search process and system logs for abrupt termination of swftools utilities (pdf2swf, swfextract, etc.) with segmentation-fault signals; correlate file-access timestamps with crash events.

What your security team should do

• Block or sandbox SWFTools execution against files from untrusted sources
• Track upstream commits for a fix and schedule upgrade once released
• Inventory all systems that ship or invoke SWFTools and remove the package where it is not required