Skip to main content
VulnerabilityPublished Updated

CVE-2024-22920: swftools · Use After Free

Affects swftoolsSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Jan 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubmatthiaskramm/swftoolspkg:github/matthiaskramm/swftoolsOther threatsAffected
  • =0.9.2
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Restrict access to swftools binaries and ensure only trusted users can execute the software.
  2. Avoid processing untrusted or unauthenticated SWF files, especially from external or unknown sources.
  3. Implement application whitelisting and sandboxing to limit the impact of potential exploitation.
  4. Monitor system logs and behavior for unusual activity related to swftools usage.
  5. Maintain up-to-date backups of critical data to enable recovery in case of compromise.
  6. Engage with the swftools community or maintainers to track the release of official patches or updates addressing this vulnerability.
  7. Consider alternative tools or workflows that do not rely on swftools for SWF processing until a patch is available.
  8. Educate users about the risks of opening or processing potentially malicious Flash content to reduce inadvertent exploitation.
  9. Employ endpoint detection and response (EDR) solutions to detect exploitation attempts involving heap corruption or anomalous swftools behavior.

Description

swftools 0.9.2 was discovered to contain a heap-use-after-free via the function bufferWriteData in swftools/lib/action/compile.c.

References

Community reviews

Loading reviews…