CVE-2022-35095

What it actually does

Local memory corruption causing a segmentation violation (crash) inside InfoOutputDev::type3D1 while parsing malformed PDF content.

Why it matters to the business

Processing of untrusted PDF or SWF files with the affected tools can crash the application, interrupting automated workflows that rely on swftools for document conversion or inspection.

How an attack unfolds

An attacker supplies a specially crafted PDF file containing malformed Type 3 font data; when swftools parses the file, the type3D1 routine dereferences invalid memory and terminates the process.

How to fix it

Upgrade to a patched build of swftools that corrects the type3D1 handling; if no official release exists, apply the upstream commit that resolves the out-of-bounds access or replace swftools with an alternative tool.

How to confirm the fix worked

Confirm the installed swftools binary is newer than commit 772e55a2, then re-run parsing against known trigger files to verify absence of the crash.

Typical attack path

1. Craft a PDF containing invalid Type 3 font structures that reach InfoOutputDev::type3D1
2. Deliver the file to a target system or service that invokes swftools binaries
3. Trigger parsing of the file, causing an immediate segmentation fault and denial of service

How to detect it

Inspect system and application logs for segmentation fault entries or core dumps generated by swftools binaries during PDF processing; correlate with file access timestamps of suspicious PDF inputs.

• InfoOutputDev::type3D1
• segmentation violation
• pdf/InfoOutputDev.cc

What your security team should do

• Remove or sandbox swftools from any automated pipelines that accept untrusted documents
• Monitor for updates or community patches addressing this crash
• Replace swftools usage with maintained alternatives where possible