CVE-2022-35105

What it actually does

Heap buffer overflow in the png2swf binary when processing a crafted PNG file, resulting in memory corruption that can lead to application crash or potential arbitrary code execution.

Why it matters to the business

Processing untrusted image files with the affected tool can cause service disruption or system compromise in environments relying on SWFTools for SWF generation workflows.

How an attack unfolds

An attacker crafts a malicious PNG file designed to trigger the heap overflow during conversion; the victim runs png2swf on the file locally, causing the overflow condition to manifest.

How to fix it

Upgrade to a patched version of SWFTools once available or replace the tool with a maintained alternative; avoid processing untrusted PNG files with png2swf until fixed.

How to confirm the fix worked

Test png2swf against known-good and known-bad PNG samples in a controlled environment; monitor for segmentation faults or abnormal memory usage during conversion; verify binary hash against upstream releases.

Typical attack path

1. Craft malicious PNG payload targeting the vulnerable png2swf code path
2. Deliver the file to the target environment via email, download, or shared storage
3. Victim executes png2swf against the file
4. Heap overflow occurs, potentially leading to crash or code execution

How to detect it

Review process execution logs and command-line history for png2swf invocations; inspect system logs for segmentation faults or heap-related errors around the time of image processing jobs.

• png2swf
• segmentation fault.*png2swf
• /bin/png2swf

What your security team should do

• Inventory all systems using SWFTools and restrict png2swf execution to trusted inputs only
• Implement file-type sandboxing or conversion in isolated containers
• Monitor for future upstream fixes and apply promptly given public exploit availability