Security readout for executives and security teams
Plain-English summary
CVE-2022-35085 is a memory leak in SWFTools at commit 772e55a2. The main business risk is denial of service when SWFTools processes a crafted or problematic file. Sources do not identify a specific supported product version, vendor fix, or active exploitation.
Executive priority
Prioritize remediation where SWFTools processes external or customer-supplied files. For internal-only, occasional use, urgency is lower but still worth addressing because the expected impact is service disruption.
Technical view
The CVE describes a CWE-401 memory leak in /lib/mem.c. CVSS 3.1 is 5.5 with local attack vector, low complexity, no privileges, required user interaction, and high availability impact only. The bundled references include a GitHub issue and a public PoC write-up path for gif2swf.
Likely exposure
Exposure is most likely where SWFTools or gif2swf is installed and used to process untrusted media files. The CVE metadata does not provide affected version ranges or CPEs, so asset validation must be based on local software inventory and project guidance.
Exploitation context
The source bundle does not show KEV listing or active exploitation. A public PoC reference is cited, but the CVSS vector indicates local access and user interaction are required. Treat this as a denial-of-service risk, not a data theft or integrity compromise issue.
Researcher notes
The public metadata is thin: affected vendor, product, versions, and CPEs are listed as n/a. The strongest supported conclusions are CWE-401 memory leak, availability impact, SWFTools commit reference, local/user-interaction exploitation model, and no KEV evidence.
Mitigation direction
- Check SWFTools project guidance and issue 181 for fixed commits or releases.
- Avoid processing untrusted files with vulnerable SWFTools builds.
- Run media conversion in isolated, resource-limited worker environments.
- Replace or update SWFTools if no maintained fix is available.
- Monitor conversion jobs for memory growth or repeated failures.
Validation and detection
- Inventory systems and pipelines using SWFTools or gif2swf.
- Determine whether builds include commit 772e55a2 or affected /lib/mem.c code.
- Review file-upload and conversion workflows for untrusted media handling.
- Confirm compensating controls limit memory consumption and process blast radius.
- Track vendor or maintainer notes for a definitive affected-version statement.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-401: 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 lookupCVE-2022-35085 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H1.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/matthiaskramm/swftools/issues/181CVE reference · x_refsource_MISC
- https://github.com/Cvjark/Poc/blob/main/swftools/gif2swf/CVE-2022-35085.mdCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.