CVE-2018-11100
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe decompileSETTARGET 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe decompileSETTARGET function in libming's decompile.c fails to validate that the actual file size matches the file size declared in the header. When processing a SWF file where the header indicates a larger size than the actual file, the function attempts to read beyond the available data, causing a segmentation fault and crash.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 0.4.8CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify libming versionRun 'pkg-config --modversion libming' or check the library file version with 'ldd' or 'dpkg -l | grep ming' on Linux systems. Alternatively, check the compiled library binary for version strings.Affected if Installed version is 0.4.8 or lower (any version <= 0.4.8)
-
Confirm decompile functionality in useIdentify if your application or tool uses the 'decompile.c' module, specifically the 'decompileSETTARGET' function. Search codebase for references to 'decompileSETTARGET' or 'decompile' from libming.Affected if Codebase imports and calls decompile functions from libming
-
Determine SWF file processing pathIdentify if your application processes SWF files. Check for file type detection logic that handles .swf extensions or SWF MIME types, and traces the file to the decompile functions.Affected if Application accepts and processes SWF files
-
Inspect header size validation logicExamine the decompileSETTARGET function in decompile.c (or the library binary) to verify if it compares the declared header file size against the actual file size before reading. Use 'strings' on the library or review source code if available.Affected if No validation exists that checks if declared header size exceeds actual file size
You are affected if you run libming version 0.4.8 or lower and process SWF files using the decompile functionality where a maliciously crafted SWF with oversized header declarations could cause a read-beyond-EOF crash.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate libming to a version with the patch, or implement input validation to reject SWF files where the declared header size exceeds the actual file size before passing files to the decompiler.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11100 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-11100 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data