LiveActive security incident?Get immediate response
CVE Record

CVE-2022-35096: SWFTools commit 772e55a2 was discovered to contain a heap-buffer overflow via draw_stroke at /gfxpoly/strok...

SWFTools commit 772e55a2 was discovered to contain a heap-buffer overflow via draw_stroke at /gfxpoly/stroke.c.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-35096 is a heap buffer overflow in SWFTools, reported in draw_stroke within gfxpoly/stroke.c. The main business risk is service disruption if vulnerable tooling processes a crafted file. Sources do not identify a fixed version or broad product/version matrix.

Executive priority

Treat this as a moderate availability risk for environments using SWFTools on untrusted files. It is not a broad internet-facing emergency based on the supplied evidence, but document-processing pipelines should be reviewed and isolated promptly.

Technical view

The CVE describes CWE-787 out-of-bounds write behavior in SWFTools commit 772e55a2. CVSS 3.1 is 5.5: local attack vector, low complexity, no privileges, user interaction required, and high availability impact. Evidence points to crash/DoS risk rather than confidentiality or integrity impact.

Likely exposure

Exposure is most likely where SWFTools, including pdf2swf-related workflows, processes untrusted or externally supplied files. The CVE record does not provide CPEs, vendor-package versions, or distribution-specific affected ranges, so inventory must focus on local SWFTools usage and provenance.

Exploitation context

The CVE is not listed as CISA KEV. A public proof-of-concept reference is cited, but the provided sources do not support active exploitation claims. The CVSS vector indicates exploitation requires local processing plus user interaction, consistent with crafted-file handling risk.

Researcher notes

The source bundle lacks exact affected versions, patch status, and maintainer remediation guidance. Analysis should remain scoped to SWFTools commit 772e55a2 and the referenced draw_stroke heap overflow. Do not infer downstream package impact without additional vendor evidence.

Mitigation direction

  • Check upstream SWFTools guidance for a fixed commit or release.
  • Avoid processing untrusted files with SWFTools until exposure is understood.
  • Run SWFTools conversion jobs in sandboxed, resource-limited environments.
  • Restrict automated ingestion paths that invoke pdf2swf or related tooling.
  • Replace or update vulnerable builds when vendor-supported fixes are available.

Validation and detection

  • Inventory systems, containers, and build images for SWFTools usage.
  • Determine whether deployed builds include or derive from commit 772e55a2.
  • Review workflows that process user-supplied PDFs or SWF-related content.
  • Check crash logs for SWFTools failures during file conversion.
  • Confirm conversion jobs have isolation and availability safeguards.
Prepared
Confidence
medium
Sources
4

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-787: 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-35096 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
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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
3Source 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
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2022-35096Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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
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-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.