CVE-2022-35091

What it actually does

A floating point exception in DCTStream::readMCURow causes the application to abort when processing a malformed input file containing invalid DCT data.

Why it matters to the business

Unexpected termination during file conversion or extraction workflows can halt automated pipelines and require manual intervention, with rising exploit probability increasing the chance of targeted disruption.

How an attack unfolds

An attacker supplies a crafted input file that reaches the vulnerable DCT stream parsing routine; when the tool attempts to decode the malformed MCU row the floating-point exception is triggered and the process terminates.

How to fix it

Replace the affected swftools installation with a patched build once available or migrate to an alternative tool; in the interim restrict processing to trusted files only.

How to confirm the fix worked

Execute the affected utilities against a test corpus containing the crashing input and confirm the process no longer terminates abnormally; review build logs for updated Stream.cc handling.

Typical attack path

1. Create or obtain a file that triggers the FPE in DCTStream::readMCURow
2. Deliver the file to a system running the vulnerable swftools binary
3. Invoke a swftools utility that processes the file
4. Observe application crash and denial of service

How to detect it

Search application and system logs for floating-point exception signals or abrupt termination of swftools binaries during file-processing jobs; correlate with file timestamps that match known malicious samples.

What your security team should do

• Block untrusted file ingestion into swftools pipelines until a fixed version is deployed
• Monitor the upstream repository for commits addressing the Stream.cc floating-point exception
• Add crash-monitoring alerts for swftools processes in production environments