CVE-2022-35088

What it actually does

Heap buffer overflow in getGifDelayTime during GIF processing allows memory corruption when parsing malformed input files.

Why it matters to the business

Local denial-of-service crashes can interrupt batch conversion or media processing workflows that rely on the affected tools, with moderate urgency given the age of the issue and available exploit code.

How an attack unfolds

An attacker crafts a malicious GIF file that triggers the overflow inside gif2swf.c when the tool parses the delay-time field; the file is supplied locally to the affected binary, causing heap corruption and potential application termination.

How to fix it

Upgrade motion packages on Debian 11/12/13/14 to version 4.3.2-1 or later; rebuild any custom SWFTools installations from a patched source tree that corrects the getGifDelayTime bounds check.

How to confirm the fix worked

Confirm the installed package version matches or exceeds the listed fixed release, then re-run conversion of known-good GIF test files to verify absence of crashes under the same workload.

Typical attack path

1. Obtain or generate a malformed GIF file sized to overflow the delay-time buffer
2. Invoke the vulnerable gif2swf conversion routine with the crafted file as input
3. Trigger heap corruption leading to process crash

How to detect it

Review application logs and crash dumps for segmentation faults or heap-related errors originating from gif2swf or motion during GIF processing; monitor for repeated local invocations of the conversion binary on untrusted input files.

What your security team should do

• Apply the 4.3.2-1 updates immediately on all Debian-based motion deployments
• Audit any internal scripts or pipelines that invoke gif2swf or related SWFTools binaries
• Add the affected binaries to vulnerability scanning inventories for future package updates