Security readout for executives and security teams
Plain-English summary
CVE-2018-8964 is a memory safety flaw in libming 0.4.8. A malicious SWF file can crash software that uses the vulnerable decompiler path, causing denial of service. The provided sources do not establish data theft, code execution, active exploitation, or a confirmed fixed version.
Executive priority
Prioritize if the organization still processes SWF files from users, partners, or automated feeds. Otherwise, treat as a legacy dependency hygiene issue with limited business urgency.
Technical view
The issue is a use-after-free in decompileDELETE within decompile.c in libming 0.4.8. The published impact is denial of service through crafted SWF input. CVSS, CWE, CPE, and affected product metadata are incomplete in the supplied record.
Likely exposure
Exposure is most likely in legacy systems, build tooling, analysis pipelines, or web services that process untrusted SWF files using libming 0.4.8. Organizations without SWF handling or libming dependency are unlikely to be exposed.
Exploitation context
The source bundle supports remote denial of service via crafted SWF input. It does not support active exploitation claims; the CVE is not listed as KEV in the provided data.
Researcher notes
The record is sparse: no CVSS vector, CWE, CPE, or patch reference is supplied. Analysis should focus on dependency discovery, SWF input trust boundaries, and confirmation against upstream libming issue 130.
Mitigation direction
- Inventory systems and dependencies for libming 0.4.8 usage.
- Avoid processing untrusted SWF files with vulnerable libming paths.
- Sandbox or isolate SWF parsing and decompilation workflows.
- Check the libming issue and project guidance for fixed versions or patches.
Validation and detection
- Confirm whether libming 0.4.8 is installed, bundled, or statically linked.
- Identify services, jobs, or tools that accept SWF input.
- Review crash logs around SWF processing or decompilation failures.
- Verify whether any vendor or project patch has been applied.
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.
CVE-2018-8964 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/libming/libming/issues/130CVE 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.