CVE-2018-13066
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 · uneditedThere is a memory leak in util/parser.c in libming 0.4.8, which will lead to a denial of service via parseSWF_DEFINEBUTTON2, parseSWF_DEFINEFONT, parseSWF_DEFINEFONTINFO, parseSWF_DEFINELOSSLESS, parseSWF_DEFINESPRITE, parseSWF_DEFINETEXT, parseSWF_DOACTION, parseSWF_FILLSTYLEARRAY, parseSWF_FRAMELABEL, parseSWF_LINESTYLEARRAY, parseSWF_PLACEOBJECT2, or parseSWF_SHAPEWITHSTYLE.
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 · moderate confidenceA memory leak exists in util/parser.c of libming 0.4.8 where multiple SWF parsing functions (including parseSWF_DEFINEBUTTON2, parseSWF_DEFINEFONT, parseSWF_DEFINESPRITE, and others) fail to properly free allocated memory during error conditions or after processing, leading to resource exhaustion and denial of service.
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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Check if libming library is installedRun 'dpkg -l | grep libming' on Debian-based systems, or 'rpm -qa | grep ming' on RHEL-based systems, or search for libming files with 'find /usr -name "*ming*" 2>/dev/null'Affected if libming 0.4.8 is found on the system
-
Verify the exact libming versionIf libming is installed, run 'pkg-config --modversion ming' or check the library file version with 'strings /usr/lib/libming.so 2>/dev/null | grep -i version' or check the package version directlyAffected if The version is exactly 0.4.8
-
Identify applications using libming for SWF parsingSearch for binaries or scripts that link to libming using 'ldd <binary> | grep ming' or 'ldconfig -p | grep ming', and review any custom applications that process SWF filesAffected if Applications process SWF files using libming 0.4.8 parsing functions such as parseSWF_DEFINEBUTTON2, parseSWF_DEFINEFONT, or parseSWF_DEFINESPRITE
-
Audit custom code referencing vulnerable parser functionsIf you have custom source code that uses libming, search for calls to parseSWF_DEFINEBUTTON2, parseSWF_DEFINEFONT, parseSWF_DEFINESPRITE or other SWF parsing functions in your codebaseAffected if Custom code directly invokes the vulnerable parsing functions from libming 0.4.8
Your environment is affected if libming version 0.4.8 is installed and any application or code uses it to parse SWF files with the vulnerable parsing functions.
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 dataUpgrade to a patched version of libming if available; otherwise, sanitize and restrict input SWF files from untrusted sources, or implement process monitoring to detect and restart services exhibiting memory exhaustion.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13066 — 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-13066 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