LiveActive security incident?Get immediate response
CVE Record

CVE-2018-11095: The decompileJUMP function in decompile.c in libming through 0.4.8 mishandles cases where the header indica...

The decompileJUMP function in decompile.c in libming through 0.4.8 mishandles cases where the header indicates a file size greater than the actual size, which allows remote attackers to cause a denial of service (Segmentation fault and application crash) or possibly have unspecified other impact.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-11095 is a libming parsing bug that can crash applications when they process a malformed file whose declared size is larger than the real file. The known impact is denial of service through application crash. The provided sources do not confirm active exploitation, a CVSS score, or a specific fixed version.

Executive priority

Prioritize review if file processing is exposed to customers or external partners. The main confirmed risk is service disruption, not confirmed data theft or code execution. If libming is absent or isolated from untrusted input, urgency is lower.

Technical view

In libming through 0.4.8, decompileJUMP in decompile.c mishandles inconsistent file size metadata. A remote attacker could provide crafted input that triggers a segmentation fault and application crash, with unspecified other impact noted but not detailed in the sources.

Likely exposure

Exposure is most likely where libming through 0.4.8 processes untrusted SWF or Flash-derived files, especially in upload, conversion, decompilation, or analysis workflows. Organizations not using libming, or using it only on trusted internal files, are less likely to be affected.

Exploitation context

The source bundle states remote attackers can cause denial of service or possibly unspecified other impact. It does not cite public exploitation, and KEV status is false. Treat exploit status as unconfirmed based on the provided evidence.

Researcher notes

Evidence is sparse: no CVSS, CWE, patch version, or detailed root-cause analysis is included in the bundle. The issue centers on trust of declared file size versus actual data length in decompileJUMP. Do not assume impact beyond crash without further vendor evidence.

Mitigation direction

  • Inventory systems and services that use libming through 0.4.8.
  • Avoid processing untrusted files with affected libming components.
  • Isolate or sandbox any file decompilation or conversion workflow.
  • Check libming project guidance for fixed versions or recommended patches.
  • Remove libming from exposed workflows if it is no longer required.

Validation and detection

  • Confirm whether libming is present in application dependencies or system packages.
  • Identify workflows that parse or decompile user-supplied SWF files.
  • Review crash logs for segmentation faults in libming decompile code paths.
  • Verify whether deployed libming versions are at or below 0.4.8.
  • Document compensating controls for any remaining affected usage.
Prepared
Confidence
medium
Sources
4

Public sources used

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.

cve · low confidence lookup

CVE-2018-11095 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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