Skip to main content
CVE-2024-25165VulnerabilityPublished Updated

CVE-2024-25165: swftools · n/a

Affects swftoolsSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 07:57 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Feb 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 2026-10-26.

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

Until an official patch is released, organizations should implement several specific mitigations: 1) Avoid processing untrusted or unauthenticated SWF files with SWFTools to reduce exposure to crafted malicious inputs. 2) Employ sandboxing or containerization to isolate SWFTools processes, limiting the impact of potential exploitation. 3) Use application whitelisting and strict execution policies to prevent unauthorized code execution stemming from exploitation. 4) Monitor network traffic and system logs for anomalous behavior indicative of exploitation attempts, such as unexpected crashes or unusual process activity related to SWFTools. 5) Where possible, replace SWFTools with more modern, actively maintained tools that do not rely on vulnerable legacy components. 6) Prepare for rapid deployment of patches once available by maintaining an inventory of affected systems and establishing update procedures. 7) Educate users about the risks of opening untrusted SWF files and enforce policies restricting their use. These targeted actions go beyond generic advice by focusing on containment, detection, and risk reduction specific to this vulnerability and the affected software.

Description

A global-buffer-overflow vulnerability was found in SWFTools v0.9.2, in the function LineText at lib/swf5compiler.flex.

References

Community reviews

Loading reviews…