LiveActive security incident?Get immediate response
CVE Record

CVE-2022-35086: SWFTools commit 772e55a2 was discovered to contain a segmentation violation via /multiarch/memmove-vec-unal...

SWFTools commit 772e55a2 was discovered to contain a segmentation violation via /multiarch/memmove-vec-unaligned-erms.S.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-35086 is an availability issue in a referenced SWFTools commit. Processing a crafted local file can trigger a segmentation violation, potentially crashing the tool. The supplied sources do not identify supported product versions, deployment scope, or an upstream fix, so urgency depends on whether SWFTools processes untrusted media in your environment.

Executive priority

Treat this as a moderate operational risk. It is mainly a crash scenario, but automated file-processing services can turn repeated crashes into service disruption. Prioritize environments handling untrusted media over isolated analyst workstations.

Technical view

The CVE describes a CWE-787 out-of-bounds write condition causing a segmentation violation in SWFTools commit 772e55a2, associated with memmove-vec-unaligned-erms.S. CVSS 3.1 is 5.5: local attack vector, low complexity, no privileges, user interaction required, and high availability impact only.

Likely exposure

Exposure is most likely where SWFTools is installed in media conversion, file ingestion, CI, or archival workflows that process externally supplied files. The bundle lists affected vendor, product, versions, and CPEs as n/a, so asset owners must confirm local usage directly.

Exploitation context

The CVE is not listed as KEV in the supplied bundle. A public PoC reference is listed, but the provided data does not establish active exploitation, remote exploitability, or compromise of confidentiality or integrity.

Researcher notes

The source data is thin: affected versions and fix status are not provided, and the description names a low-level memmove crash rather than a precise SWFTools code path. The PoC reference suggests public reproducibility, but analysis should avoid assuming broader impact without upstream confirmation.

Mitigation direction

  • Inventory SWFTools installations and determine whether commit 772e55a2 or related builds are present.
  • Avoid processing untrusted media with SWFTools until vendor guidance is confirmed.
  • Run conversion jobs in a sandboxed, least-privilege environment with resource limits.
  • Check the upstream GitHub issue and CVE record for any fixed release or workaround.
  • Prioritize remediation for internet-facing upload or automated file-processing pipelines.

Validation and detection

  • Confirm whether SWFTools is installed on servers, workstations, CI runners, or conversion workers.
  • Identify workflows that feed user-supplied files into SWFTools components.
  • Review crash logs for segmentation faults during SWFTools media processing.
  • Compare deployed builds against the referenced commit and upstream project history.
  • Document whether any compensating sandboxing or isolation controls are already enforced.
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-35086 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-35086Attack 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.