CVE-2022-35087

What it actually does

The flaw triggers a segmentation violation during MovieAddFrame processing in /src/gif2swf.c, causing memory corruption that crashes the process and denies availability.

Why it matters to the business

Processing malformed input files can unexpectedly crash affected tools or libraries, interrupting workflows and requiring restarts or updates; low EPSS and no KEV status indicate limited real-world urgency despite 1488 days since publication.

How an attack unfolds

An attacker supplies a specially crafted input file that reaches the vulnerable MovieAddFrame code path, causing the segmentation fault; no named threat actors or ransomware usage reported.

How to fix it

Upgrade chaijs/pathval to commit db6c3e39c39859564704b7f37149082689f1b172 and node-pathval on Debian 11/12/13 to version 1.1.0-4; apply updates promptly given exploit availability.

How to confirm the fix worked

Confirm the installed version matches a fixed commit or package version listed above; re-test with known triggering input files to verify absence of the segmentation violation.

Typical attack path

1. Identify a target system using an affected version of the vulnerable component
2. Craft or obtain a malicious file that triggers the segmentation violation
3. Cause the target to process the file via local execution or user interaction
4. Observe denial-of-service crash

How to detect it

Review application and system logs for unexpected crashes or segmentation faults when processing GIF or similar input files; correlate with process termination events around the vulnerable binary.

What your security team should do

• Prioritize patching affected pathval and SWFTools deployments to the listed fixed versions
• Monitor EPSS trend (stable at ~0.003) and revisit if exploit maturity increases
• Restrict local file processing of untrusted inputs until patched