Skip to main content
VulnerabilityPublished Updated

CVE-2024-22913: SWFTools · Out-of-bounds Write

Source 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.3% chance of exploitation in 30 days – higher than 29% 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. Inventory and Audit: Identify all instances of SWFTools usage within the organization, including legacy systems and development environments.
  2. Restrict Access: Limit local access to systems running SWFTools to trusted users only, employing strict access controls and monitoring.
  3. User Awareness: Educate users about the risks of opening or processing untrusted SWF files, emphasizing the need to avoid interacting with suspicious content.
  4. Isolation: Run SWFTools in sandboxed or isolated environments (e.g., virtual machines or containers) to contain potential exploitation impact.
  5. Monitoring and Detection: Implement host-based intrusion detection systems (HIDS) and monitor for anomalous behavior indicative of exploitation attempts.
  6. Patch Management: Continuously monitor for official patches or updates from SWFTools maintainers and apply them promptly once available.
  7. Alternative Tools: Where feasible, transition to alternative, actively maintained tools for SWF processing that do not exhibit this vulnerability.
  8. Incident Response Preparedness: Prepare and test incident response plans to quickly address potential exploitation scenarios involving this vulnerability.

Description

A heap-buffer-overflow was found in SWFTools v0.9.2, in the function swf5lex at lex.swf5.c:1321. It allows an attacker to cause code execution.

References

Community reviews

Loading reviews…