CVE-2023-37644: Out-of-bounds Write
Source CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 09:08 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% 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:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
GitHubmatthiaskramm/swftoolspkg:github/matthiaskramm/swftoolsOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate this vulnerability, European organizations should first identify any usage of SWFTools, particularly version 0.9.2, within their environments. Since no official patches are currently linked, organizations should consider the following specific actions: 1) Restrict access to systems running SWFTools to trusted users only, minimizing the risk of malicious document processing. 2) Implement strict input validation and scanning of documents before processing with pdf2swf to detect and block potentially crafted PNG chunks. 3) Where possible, replace or phase out SWFTools in favor of more modern and actively maintained document conversion tools that do not exhibit this vulnerability. 4) Monitor application logs and system memory usage for signs of abnormal behavior or crashes related to document processing. 5) Employ sandboxing or containerization to isolate the document conversion process, limiting the impact of potential crashes or memory exhaustion. 6) Educate users about the risks of opening or processing untrusted documents with vulnerable tools, emphasizing the need for caution and verification.
Description
SWFTools 0.9.2 772e55a allows attackers to trigger a large memory-allocation attempt via a crafted document, as demonstrated by pdf2swf. This occurs in png_read_chunk in lib/png.c.