Skip to main content
VulnerabilityPublished Updated

CVE-2024-22911: 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 26% 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. Immediate identification and inventory of all systems running SWFTools v0.9.2 or earlier versions to assess exposure.
  2. Restrict local access to systems with SWFTools installed to trusted users only, minimizing the risk of exploitation requiring local access.
  3. Educate users about the risk of interacting with untrusted SWF files or executing SWFTools commands without verification to reduce the likelihood of user interaction-based exploitation.
  4. Monitor for updates or patches from the SWFTools community or maintainers; apply patches promptly once available.
  5. As a temporary workaround, consider disabling or removing SWFTools where feasible, or replacing it with alternative tools that do not have this vulnerability.
  6. Implement application whitelisting and endpoint protection solutions that can detect or block anomalous behavior related to SWFTools exploitation attempts.
  7. Conduct regular security audits and vulnerability scans focusing on legacy multimedia processing tools to identify similar risks.
  8. Establish strict file handling policies for SWF files, including scanning for malicious content before processing.

Description

A stack-buffer-underflow vulnerability was found in SWFTools v0.9.2, in the function parseExpression at src/swfc.c:2602.

References

Community reviews

Loading reviews…