CVE-2022-35080

What it actually does

Heap-buffer overflow in png_load at /lib/png.c causes memory corruption leading to application crash (high availability impact, no confidentiality or integrity loss).

Why it matters to the business

Processing of untrusted image files with the affected conversion tools can trigger crashes, disrupting automated media or document workflows that rely on the software.

How an attack unfolds

An attacker crafts a malicious PNG file that triggers the overflow when loaded via png_load; the file is opened locally by the affected tool, resulting in a crash. Public exploit code is available.

How to fix it

Upgrade SWFTools to a build containing the fix for commit 772e55a2 or later; alternatively, avoid processing untrusted PNG files with the affected tools until a patched release is obtained.

How to confirm the fix worked

Inspect source for the png_load implementation in /lib/png.c, recompile with the corrected commit, and test against known crashing PNG samples to confirm absence of the overflow.

Typical attack path

1. Craft a specially malformed PNG image targeting the png_load buffer handling
2. Deliver the image to a system running the vulnerable SWFTools binaries
3. Open or convert the file using a tool that invokes png_load
4. Trigger the heap overflow and cause denial of service

How to detect it

Monitor process crash logs and application fault reports for SWFTools binaries invoked on PNG inputs; correlate file-open events with subsequent segmentation faults or heap-related errors in system logs.

• swftools png_load crash
• heap-buffer-overflow in /lib/png.c

What your security team should do

• Treat as low-urgency given low EPSS and lack of KEV status but still restrict use on untrusted inputs
• Scan build pipelines and developer workstations for presence of the vulnerable SWFTools binaries
• Replace or sandbox the tool where possible until a confirmed fixed version is deployed