LiveActive security incident?Get immediate response
CVE Record

CVE-2022-40009: SWFTools commit 772e55a was discovered to contain a heap-use-after-free via the function grow_unicode at /l...

SWFTools commit 772e55a was discovered to contain a heap-use-after-free via the function grow_unicode at /lib/ttf.c.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2022-40009 is a reported heap-use-after-free in SWFTools source commit 772e55a. The public record rates it critical, but the source bundle does not identify supported affected versions or a named fix. Business urgency depends on whether SWFTools or derived code processes untrusted content in production workflows.

Executive priority

Prioritize rapid inventory and containment. If SWFTools handles customer-supplied or internet-originated files, treat this as urgent until upgraded, removed, or isolated. If SWFTools is absent, document non-exposure and monitor upstream guidance.

Technical view

The flaw is CWE-416 in grow_unicode within /lib/ttf.c. The CVSS 3.1 vector is 9.8 critical: network, low complexity, no privileges, no user interaction, unchanged scope, high confidentiality, integrity, and availability impact. Source detail is limited to the CVE metadata and GitHub issue reference.

Likely exposure

Exposure is most likely where SWFTools at or derived from commit 772e55a is installed, embedded, or used in automated file conversion or parsing paths. The bundle lists affected vendor/product as n/a, so teams must confirm local usage rather than rely on a complete affected-products list.

Exploitation context

No CISA KEV listing is provided, and the bundle does not cite active exploitation. The public CVSS vector indicates serious theoretical exploitability, but the supplied evidence does not establish exploitation in the wild or provide a verified patch status.

Researcher notes

Evidence is sparse. The record identifies a heap-use-after-free location and high CVSS score, but not affected release ranges, exploit maturity, or remediation details. Validate against the referenced issue and local source provenance before making broad exposure claims.

Mitigation direction

  • Inventory systems and containers for SWFTools or derived builds.
  • Check the GitHub issue and upstream guidance for fixed commits or releases.
  • Avoid processing untrusted files with vulnerable SWFTools builds.
  • Isolate conversion workflows with least privilege and sandboxing.
  • Monitor processing services for crashes or unexpected memory faults.

Validation and detection

  • Confirm whether deployed source includes commit 772e55a or derived /lib/ttf.c code.
  • Review SBOMs, package manifests, and build logs for SWFTools usage.
  • Map which services process externally supplied files through SWFTools.
  • Verify whether upstream has published a corrected commit or release.
  • Check whether any local compensating controls restrict untrusted input processing.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-416: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-40009 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2022-40009Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.