CVE-2017-11730
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 · uneditedA heap-based buffer over-read was found in the function OpCode (called from decompileINCR_DECR line 1474) in util/decompile.c in Ming 0.4.8, which allows attackers to cause a denial of service via a crafted file.
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 heap-based buffer over-read vulnerability exists in the OpCode function in util/decompile.c of Ming library 0.4.8. The flaw is triggered when parsing crafted SWF files through the decompileINCR_DECR function (line 1474), allowing attackers to read beyond buffer boundaries and cause a 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 installed Ming library versionRun 'ming-getversion' or check package manager for ming-libs package (dpkg -l | grep ming, rpm -q ming-libs, or brew list ming)Affected if Version returned is exactly 0.4.8
-
Identify Ming development filesLocate libming-dev or ming-dev package headers: find /usr/include -name 'decompile.h' 2>/dev/null, and check if util/decompile.c source file exists in any source treeAffected if Source file util/decompile.c from Ming 0.4.8 is present in the environment
-
Detect SWF processing utilitiesIdentify tools that use Ming for SWF parsing: which swfdump, swfextract, swf2json, or any custom binaries linked against libming (ldd <binary> | grep -i ming)Affected if SWF decompiling or parsing tools using libming are installed and executable
-
Check for vulnerable code pathIf source is available, examine util/decompile.c around line 1474 in the decompileINCR_DECR function for the OpCode buffer read operationAffected if The decompileINCR_DECR function and OpCode function handle untrusted SWF input without bounds validation at line 1474
-
Confirm SWF file processing occursReview application logs or audit trail for .swf file parsing activity, or check if applications accept SWF input from untrusted sourcesAffected if The environment processes SWF files through Ming-based decompilation routines
Environment is affected only if running Ming version exactly 0.4.8 and processing untrusted SWF files through the decompiler OpCode function.
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 dataAvoid processing untrusted or crafted SWF files with the Ming library. If a patched version is available, upgrade promptly. Otherwise, implement bounds checking in the OpCode function to validate buffer limits before read operations.
- Consultation3.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11730 — 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-2017-11730 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